gpu-router

Overview Schema Source Related Servers Discussions Admin

Gpu Fetch

gpu_fetch

Idempotent

Ensure a finished GPU job's outputs are on this Mac and list them, downloading again only when missing or requested; unfinished jobs show where outputs will land.

Instructions

Make sure a finished job's outputs are on this Mac and list them. Outputs are downloaded automatically when a job finishes, into /runs// (outputs_dir); this call lists what is there (path + bytes, first 100 files) and downloads again only when they are missing or refetch=true. Waits up to wait_s (default 45, max 300) for a download; if it is still going, the result says in_progress=true: call again. For a job that has not finished it returns fetched=false and says where outputs will land. Returns the CLI gpu fetch --json shape: {"job", "fetched", "outputs_dir", "files" (count), "message", "outputs"}.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	Yes	Job id or unique prefix (job.short_id, e.g. a7f2).
`wait_s`	No	Seconds to wait for a download (default 45).
`refetch`	No	Download again even when the outputs are on disk.
`verbose`	No	Return the full documents (null fields, every event) instead of the trimmed ones.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: discloses that it only downloads when files are missing or refetch=true, caps listing at the first 100 files, waits up to wait_s (default 45, max 300), and returns in_progress=true with a retry instruction if the download is still running. Annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) are consistent with this re-download-only-when-needed behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose in the first sentence and keeps every subsequent sentence substantive (download conditions, wait/retry semantics, unfinished-job behavior). The closing sentence restating the JSON return shape is somewhat redundant given an output schema exists, but it is brief.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a fetch/poll tool with a full output schema, four well-documented params, and annotations, the description covers the decision-relevant behavior: when a download happens, how long it blocks, how to retry, and what an unfinished job yields. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: it explains the refetch=true trigger condition, the wait_s budget and default, and how ref accepts a job id or short_id prefix. That is meaningful context beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: verify a finished job's outputs are on the local Mac and list them. The scope (finished jobs, local output directory) distinguishes it from siblings like gpu_status or gpu_logs, and the fallback behavior for unfinished jobs is made explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the normal flow (outputs download automatically on completion), when this call is actually needed (missing files or refetch=true), and what to do when a job is unfinished. It does not name an alternative sibling tool by name, but the conditions that select this tool are unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server