Retrieve specific model version details, including metrics, stage, and run ID, by providing model name and version.
Get specific model version details (metrics, stage, run_id)
| Name | Required | Description | Default |
|---|---|---|---|
| version | Yes | ||
| model_name | Yes |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true already indicates a safe read operation. The description adds value by specifying the returned fields (metrics, stage, run_id). No contradictions and no missing behavioral cues like error conditions or permissions for a simple getter.
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 with no superfluous words. The key information (action, resource, returned data) is front-loaded and immediately useful.
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?
Given the simplicity of the tool and the presence of readOnlyHint, the description is adequate but not comprehensive. It lacks guidance on distinguishing from similar siblings like 'get_model_version_by_alias' and does not mention what happens if the version does not exist.
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%, so the description must compensate. It does not explain the meaning or format of 'model_name' or 'version' beyond implying they identify the version. No additional constraints or examples are provided.
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 the verb 'get', the specific resource 'model version', and lists the details returned (metrics, stage, run_id). It differentiates from sibling tools like 'get_model_versions' (plural) and 'get_latest_versions'.
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?
No explicit guidance on when to use this tool versus alternatives. The description implies usage when you have a specific version identifier, but does not mention disambiguation from tools like 'get_model_version_by_alias' or 'get_latest_versions'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.