Retrieve a stored Detect Agent investigation run by its run ID to access results and details from a prior deepfake detection or media authenticity check.
Fetch a persisted Detect Agent investigation run by run_id.
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes | ||
| agent_uuid | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must carry the full behavioral burden. 'Fetch' implies a read-only operation, but it does not disclose potential errors (e.g., missing run), permission requirements, or any side effects. For a simple getter, this is acceptable but minimal.
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, front-loaded sentence with zero wasted words. It states the core action and target clearly.
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?
Since an output schema exists, return values are not needed. However, the description omits any explanation of the agent_uuid parameter and doesn't clarify that this fetches a single persisted run as opposed to a list. For a simple getter, this is borderline adequate.
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 schema has 0% description coverage, so the description is the only source of parameter meaning. It mentions run_id but does not explain agent_uuid, its purpose, or any format constraints. This is insufficient for a tool with two required parameters.
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 'fetch' and the resource 'persisted Detect Agent investigation run', which distinguishes it from listing runs or getting detections. However, it doesn't explicitly contrast with sibling tools like resemble_list_investigation_runs, so it's clear but not fully differentiated.
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 guidance is provided on when to use this tool versus alternatives. It does not mention that this fetches a single run by ID, while resemble_list_investigation_runs lists runs, or that this is for retrieving a persisted run rather than creating one. The description is purely definitional.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.