Skip to main content
Glama

wait_for_download

Waits for a file download triggered by a click to finish, then returns its path on disk so agents can use the downloaded invoice, CSV, or PDF.

Instructions

After clicking something that downloads a file (an invoice, a CSV export, a PDF), wait for it to finish and get its path on disk. Downloads that started in the last 15 seconds count, so call it right after the click.

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": "wait_for_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
browserNo
timeout_secondsNoDefault 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose two non-obvious traits: only downloads started within the last 15 seconds are considered, and the result is a filesystem path. It omits what happens on timeout (raise an error, return nothing?) and whether it blocks or polls the remaining budget, which is the main behavioral gap.

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?

Two short sentences, front-loaded with the trigger and followed by the timing constraint. The parenthetical examples earn their place by making the file-type scope concrete, and there is no filler.

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?

Because no output schema exists, the description correctly explains the return value (path on disk) and the recency window, which an agent could not learn elsewhere. Only the failure/timeout outcome is left unstated for a tool whose entire job is bounded waiting.

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?

Schema coverage is 67% – tab carries an example handle and timeout_seconds documents its default of 60, while browser is undocumented. The description mentions no parameters at all, so it adds nothing beyond the schema; the baseline 3 for moderate coverage is appropriate.

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

Purpose4/5

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

States a specific verb ('wait for it to finish') and resource ('a file ... an invoice, a CSV export, a PDF'), and adds the return value ('get its path on disk'). It implicitly separates itself from download_file (which starts a download) and list_downloads (a listing), but never names them, so the differentiation is inferred rather than stated.

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?

Gives a concrete trigger condition ('after clicking something that downloads a file') and an operational rule ('call it right after the click') backed by the 15-second lookback. It does not say when NOT to use it (e.g. for downloads already finished earlier, where list_downloads would apply), so no exclusions or named alternatives.

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