List local browser download receipts for CSMAR or CNRDS data exports, optionally waiting up to 30 seconds to detect new saved files.
List this session's local export receipts; optionally wait 0–30 seconds.
Previously saved files/manifests persist on disk when the server restarts. This tool reports browser downloads, not provider-side export job progress.
| Name | Required | Description | Default |
|---|---|---|---|
| provider | Yes | ||
| wait_seconds | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile is covered. The description adds valuable context beyond annotations: persistence across restart, and crucially that it reports browser downloads rather than server/provider progress. It does not mention pagination or receipt format, but the added behavioral context is substantive.
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?
Three short, front-loaded sentences with no wasted phrasing; the scope statement and the 'browser downloads, not provider progress' distinction come early. Slightly fragmented but efficient.
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?
No output schema exists, so the description should clarify what receipts contain, but it does not. For a read-only listing tool the safety and scope are adequately conveyed, but with 0% param coverage and no return-value description, it falls short of 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%, so the description must compensate. It explains wait_seconds (wait 0–30 seconds) usefully, but says nothing about the required 'provider' parameter or its enum values (csmar/cnrds), leaving the most important disambiguation undocumented.
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 and resource: it lists this session's local export receipts, and explicitly scopes it to 'browser downloads, not provider-side export job progress.' However, it does not name the sibling it differs from (e.g., campus_export), leaving the boundary slightly implicit.
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?
It gives a clear exclusion ('not provider-side export job progress') that helps disambiguate from export-job tools, and hints the wait option. But it does not state when to prefer this over campus_inspect or campus_export, nor when to set wait_seconds versus polling later.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.