Skip to main content
Glama

Download a file

cotlet_browser_download
Destructive

Gets the file that clicking element (a download link or button) or opening url starts, also an image or PDF it only opens: answers its name, type, size and a link valid 15 minutes; CSV, JSON and other text files also as text.

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

Input Schema

NameRequiredDescriptionDefault
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
tabNoThe Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.
urlNoA public http or https address, e.g. https://example.com.
elementNoThe element's number from the last read or step answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tab
      Added value: +{
      +  "description": "The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, and the description adds genuinely useful behavior: the answer includes name, type, size and a link valid 15 minutes, and text-like files come back as text. However, it never explains what makes the call destructive or irreversible, nor whether the download itself is committed server-side, so a key annotation-driven risk remains unexplained. The tab_changed abort behavior lives only in the schema.

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?

A single dense sentence, front-loaded with the action, then the return payload, then the text-file exception. Every clause carries information; the only cost is that the colon-and-semicolon construction is slightly hard to parse on first read.

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?

There is no output schema, so the description carries the return-value burden and does so adequately: name, MIME type, size, a 15-minute link, and inline text for CSV/JSON. Missing pieces are failure modes (no file started, element not a download) and any note on the destructive flag, but for a four-parameter optional-input tool this is close to complete.

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 100%, so `app`, `tab`, `url` and `element` are already fully documented. The description adds a modest amount — that `element` must be a download link or button and that `url` is an alternative trigger for the same result — but gives no detail on how the two interact when both are supplied. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description names a concrete verb and outcome: it 'gets the file' that a click on `element` or an open of `url` starts, and it covers the read-only variants (image/PDF preview). That clearly distinguishes it from cotlet_browser_click and cotlet_browser_read, which merely act on or read a page rather than returning the downloaded artifact. It stops short of a 5 because no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied through the two entry paths: pass `element` for a download link/button from the last read, or `url` to open an address. There is no explicit 'use this instead of cotlet_browser_click when...' statement, and no guidance on what happens when neither triggers a file, so the agent must infer the selection rule.

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