Find which MIKE Zero engine runs a given file extension by checking MzEngines.cfg mappings. Filter by extension or version year to get the exact engine association.
列出 MIKE Zero 的 扩展名 -> 引擎 映射（来自 MzEngines.cfg）。
Args: extension: 可选，只看某个扩展名，如 ".m21fm"。 year: 可选，指定 MIKE Zero 年份。
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| extension | No |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. '列出' implies a read-only listing operation, and the mention of MzEngines.cfg adds useful source context, but side effects, error behavior, and output format are not disclosed.
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?
The description is compact and well-structured, with the purpose front-loaded and parameter details presented in a clear Args block. Every sentence earns its place.
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 simple two-optional-parameter list tool, the core invocation details are present, but with no output schema and no annotations, the return shape and the exact effect of the year filter are left unspecified. Adequate but not fully complete.
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?
Schema description coverage is 0%, and the description compensates by explaining both parameters: extension is optional and demonstrated with '.m21fm', and year is optional and scopes the MIKE Zero version. This adds real meaning beyond the bare schema.
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 clearly states a specific verb ('列出' / list) and a concrete resource ('扩展名 -> 引擎 映射' from MzEngines.cfg). It clearly identifies what the tool does, though it does not explicitly contrast itself with any sibling tool.
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?
There is no guidance about when to use this tool versus alternatives, nor any exclusions or prerequisites. The Args section explains parameters but not usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.