Retrieve a bounded snapshot of Unreal Engine actors with stable paths and transforms. Use queries and limits to inspect the current scene without making cloud calls.
Read a bounded actor snapshot with stable paths and transforms; no cloud call.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already communicate read-only and non-destructive behavior, so the description correctly avoids repeating those. It adds useful behavioral context by disclosing that the tool makes no cloud call and that returned paths/transforms are stable, which informs latency and result reliability expectations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence front-loads the core operation and then adds two meaningful operational constraints. Every phrase earns its place and there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool itself is simple, read-only, optional-parameter-only, and has an output schema, so the core call is usable. However, among roughly 50 sibling tools, the lack of selection guidance and the absence of query-parameter semantics leave a meaningful gap for an agent deciding when and how to invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description needed to compensate for the undocumented parameters. 'Bounded' only weakly hints at the limit parameter, and the query parameter's filtering behavior is left entirely undefined. The description adds almost no semantic value beyond the schema's property names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Read') and a bounded resource ('actor snapshot') while adding distinguishing constraints: stable paths/transforms and no cloud call. This clearly separates it from asset, workflow, and preview siblings even without naming them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The use case is implied: read a bounded, local actor snapshot. The phrase 'no cloud call' hints at when this might be preferred, but the description gives no explicit guidance on when not to use it or which alternatives like unreal_actor_details or unreal_snapshot should be chosen instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.