Check if an export job has finished and where its file is by passing the job ID. Use it to monitor report exports and retrieve completed files.
Check whether an export job has finished and where the file is.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | 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, the description carries the full behavioral burden. It usefully discloses the return content (finished? + file location), but says nothing about permission requirements, polling frequency, status values, or whether the file expires.
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 efficient sentence with the two key outputs front-loaded. No padding, though it is arguably under-specified rather than optimally concise.
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?
Without an output schema or annotations, the description must carry more. It conveys the core return contract but omits status enumeration, error/not-found behavior, and how the resulting file location pairs with download_report.
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 never mentions the job_id parameter. While 'job_id' is fairly self-explanatory as a name, the description adds no format, sourcing, or usage detail to compensate for the coverage gap.
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 ('Check') and resource ('export job'), and names the two pieces of information returned: completion state and file location. It is clearly distinguishable from list_available_reports and download_report, though it does not explicitly reference 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?
No when-to-use guidance is given. An agent can infer this is a polling tool to run after starting an export, but the description never states that, nor does it relate the tool to download_report (which presumably consumes the file location this tool returns).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.