Skip to main content
Glama

Data Cleaner

Download a table as a file

export

Get a DOWNLOAD LINK for a table you hold, as a file: csv, xlsx (Excel), json or parquet. This is how the user gets their cleaned data, or a wrangle / sql_query result, OUT -- the whole table, not a page of it. Give the user the download_url exactly as returned; it opens in a browser or with curl, and needs no key.

The link works for ONE HOUR and then stops; call export again for a fresh one (the table itself stays for as long as its table_id does). Anyone holding the link can download the file during that hour, so hand it to the user and to nobody else. The link does not reveal the table_id.

Do NOT page a table with rows to reproduce it in the conversation when the user wants the file: call export. filename names the downloaded file (letters, digits, dot, dash, underscore); the format's extension is added for you.

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": {
      "table_id": "<table_id>"
    },
    "name": "export"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo'csv', 'xlsx', 'json' or 'parquet'csv
filenameNoname of the downloaded file, without or with the extension
table_idYesthe table to export

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations, it discloses the critical behaviors: the link expires after ONE HOUR, you must call export again for a fresh one, the link needs no key, and anyone holding it can download for that hour. It also clarifies the link does not reveal the table_id, which is meaningful security context no annotation provides.

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?

The useful information is front-loaded: purpose and format first, then lifetime/security constraints, then the routing rule and parameter notes. It is multi-paragraph but every sentence carries a distinct, actionable constraint.

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 3-parameter export tool with an output schema, the description covers the remaining gaps: lifetime, re-issuance, access model, and how to hand the result to the user. Nothing an agent needs to invoke it correctly is left unstated.

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 100%, so the baseline is 3, but the description adds real meaning for `filename`: the allowed character set (letters, digits, dot, dash, underscore) and that the format's extension is appended automatically. `format` and `table_id` carry no extra detail beyond the schema, which is acceptable given full coverage.

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 opens with a specific verb and resource: 'Get a DOWNLOAD LINK for a table you hold, as a file.' It distinguishes itself from siblings by naming `rows` and stating scope explicitly ('the whole table, not a page of it'), and it lists the concrete output formats.

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

Usage Guidelines5/5

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

It says exactly when to use this tool vs the `rows` sibling: 'Do NOT page a table with `rows` to reproduce it in the conversation when the user wants the file: call export.' It also names the use cases that lead here (cleaned data or a wrangle / sql_query result).

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