Inspect a component's geometry, model parameters, feature origins, state fingerprint, and affected occurrence paths to understand its current configuration.
Inspect an existing component's native/proxy geometry, model parameters, feature origins, state fingerprint and all affected occurrence paths.
| Name | Required | Description | Default |
|---|---|---|---|
| document_id | Yes | ||
| occurrence_path | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description must carry the behavioral burden itself. 'Inspect' implies read-only, and the listed outputs clarify what the caller gets backcher. However, it does not explicitly state that no mutations occur, nor does it warn about potentially large result sets from traversing all affected occurrence paths.
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?
One dense, front-loaded sentence communicates the action, the target, and the scope of returned information without repetition or 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?
For a two-parameter inspection tool, the description gives a good high-level picture and a list of returned context categories热的, but it does not describe the return shape, failure modes, or whether the operation can be expensive. It is adequate but incomplete.
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?
The input schema has no parameter descriptions (0% coverage). The description mentions 'occurrence paths' as an output, which loosely connects to the occurrence_path parameter, but it does not explain how document_id or occurrence_path should be formatted, what they refer to, or how they interact. The description does not compensate for missing parameter docs.
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 uses a specific action ('Inspect') with a clear resource ('an existing component') and enumerates the exact kinds of context returned: native/proxy geometry, model parameters, feature origins, state fingerprint, and affected occurrence paths. This strongly distinguishes its purpose even without naming siblings.
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 description gives no explicit guidance on when to use this tool versus siblings like fusion_model_overview, fusion_query_entities, or fusion_edit_component_parameters. It also omits prerequisites or exclusion criteria. 'Existing component' is the only implicit usage signal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.