Skip to main content
Glama

export_dataset

Export a previously returned data_ref to json or xlsx without rerunning the query. Use this for standard Excel exports of reports already shown, rather than rebuilding their JSON with Python. Financial XLSX uses shared server formatting and retains source/region metadata for add-in conversion. Returns a temporary file/download link; an expired snapshot requires a fresh authorized query, whose values may change.

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": {
      "data_ref": "<data_ref>",
      "format": "<format>"
    },
    "name": "export_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYes
data_refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, it says no query is rerun, that Financial XLSX uses shared server formatting and keeps source/region metadata for add-in conversion, that a temporary file or link is returned, and that expired snapshots need a fresh authorized query whose values may change. This is exactly the side-effect and lifecycle information the annotations (readOnlyHint false, destructiveHint false, openWorldHint false) do not convey.

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?

Four sentences, each front-loaded with the operational detail that matters (cost saving, output format choice, metadata, expiry). Some phrasing is dense ('shared server formatting... for add-in conversion'), but nothing is 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?

For a two-parameter tool with no output schema, the description covers the important unknowns: what gets produced (temporary file/download link), what is preserved (metadata), and what happens on expiry. The remaining gap is provenance: it doesn't say which sibling tools yield a usable data_ref.

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 0%, so the description must compensate, and it does partly: it reveals the format values (json or xlsx) and that data_ref is a previously returned reference. But it never says which tools return a data_ref or what its shape is, and format is left as an unconstrained string in the schema.

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 specific verb and resource (export a data_ref to json or xlsx) and adds the key differentiator that it works 'without rerunning the query.' It doesn't identify which sibling produces the data_ref or how it differs from get_file_download, so it stops short of full sibling-level differentiation.

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?

It gives a clear when-to-use case (standard Excel exports of reports already shown) and an explicit when-not (rebuilding JSON with Python). It doesn't mention the alternative tool, get_file_download, which appears in the sibling list and may be the more natural choice for retrieving a produced file.

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.