ИБ
CV
Back to workWork / Unity MCP Efficient

Unity MCP Efficient

A smaller tool interface with access to the full operation catalog

Facade design and implementation
MCPTool discoveryRU/EN tool searchSchemas on demandContext optimizationBounded resultsBatch executionStored results
01 / The challenge

The challenge

A large model-visible tool surface consumed context before an agent could choose the operation it needed.

02 / How I approached it

How I approached it

I separated discovery from execution, loading operation schemas on demand and bounding returned results. Batches, stored results, receipts and idempotent retries address repeated mutations, asynchronous work and Unity domain reloads.

System flow

  1. Discover

  2. Load schema

  3. Execute

  4. Inspect result

03 / The outcome

The outcome

The published author benchmark of 24 August 2026, against upstream v10.1.0, records 48 → 6 model-visible tools and access to 377 operations. Schema context falls from 23,280 to 915 estimated tokens (characters ÷ 4); this is a documented estimate, not an independently reproduced runtime or cost benchmark.

04 / Tools & technologies

Tools & technologies

MCPTool discoveryRU/EN tool searchSchemas on demandContext optimizationBounded resultsBatch executionStored resultsReceiptsIdempotencyRetry semanticsDuplicate mutation protectionUnity domain reloadAsynchronous operationsState inspectionCompatibility layers
Continue exploring

MySellerHub

Contact

Complex challenge? Let’s make it work.

Architecture, technical leadership, or a product that needs a solid foundation.

Telegram Read CV

Start a conversation

A role, a product, or a technical challenge. Share a little context.

To use the form, enable JavaScript. You can also write to me directly on Telegram.

Write on Telegram