Skip to main content
Glama
Podcast MCP
by calebn

model_download_status

Check the status of a model download started in Podcast MCP, including running state, current file, and failure details; omit the job ID to use the default job.

Instructions

Report a model download started by model_download: status, current file and any failure.

Omit job_id for the latest download. Only the ShareCut Studio process has download jobs; anywhere else (a stdio server, even with Studio running) the answer is {"running": false}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "model_download_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load, and it does disclose real behavior: the tool reports progress and failures, tracks a specific job or the latest one, and deterministically returns {"running": false} when no job system exists in the current process. It does not describe how finished or failed jobs are represented, though the output schema covers the response shape.

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?

Three short sentences, front-loaded with purpose before the default-behavior and environment caveats; every sentence adds information. Minor friction from the literal backtick markup around job_id, but nothing is wasted.

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

Completeness4/5

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

An output schema exists, so return fields need not be restated, and the description supplies the two facts the schema and annotations cannot: the default-to-latest behavior and the process-scoped limitation. The only gap is guidance on repeated polling versus a terminal state.

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 description coverage is 0%, so the single job_id parameter is undocumented in the schema; the description compensates by explaining that omitting it selects the most recent download, which is the key semantic an agent needs. It does not say where a job_id comes from (presumably the model_download response), but the added meaning is substantial for a one-parameter tool.

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 (report) and resource (a model download started by model_download), and enumerates what is reported: status, current file, and failure. This makes it clearly distinguishable from the sibling model_download, which starts the job rather than reporting on it.

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 one decision an agent must make — omit job_id to get the latest download — and names the environment condition under which the tool is useless (outside the ShareCut Studio process it always answers {"running": false}). What is missing is any polling or frequency guidance, and it does not explicitly say to call this after model_download.

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

Deploy Server

Other Tools