Skip to main content
Glama

Check download

check_download
Read-only

Wait for a download started by download_video and return its link when ready.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "check_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesjob_id from download_video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the important behavioral fact that this call blocks/waits until the download is ready rather than returning immediately, which an agent cannot infer from the schema. It is silent on timeout, retry, and failure behavior, which keeps it below a 5.

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

Conciseness5/5

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

A single sentence with zero filler, front-loading the blocking behavior and ending with the return value. Every clause carries information the agent needs.

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?

For a one-parameter, non-destructive polling tool with no output schema, the description covers the essential flow: it waits, it is tied to download_video, and it yields a link. It leaves out how a not-ready or failed job manifests, which is the main remaining gap given there is no output schema to describe error shapes.

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

Parameters3/5

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

There is one parameter with 100% schema description coverage, and the schema already says job_id comes from download_video. The description echoes that relationship but adds no new detail about the identifier's format or lifetime, so the schema does the heavy lifting and the baseline 3 applies.

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?

The description states a specific verb (wait/check), the resource (a download started by download_video), and the outcome (returns its link when ready). It also implicitly distinguishes itself from the sibling that initiates the job, so an agent can tell the two apart without opening either schema.

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?

"Wait for a download started by download_video" gives a clear precondition: call this only after download_video has been invoked and returned a job. It does not state how often to poll, whether repeated calls are expected, or what to do if the link never becomes ready, so no explicit when-not guidance is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources