Skip to main content
Glama

Export a pull to a file

export

Export a saved pull to a CSV or Excel file by re-running its stored SQL and writing every row; returns only the file path.

Instructions

Export a past pull to a file on the user's machine: format 'csv' or 'xlsx' (Excel). Runs the pull's stored SQL again and writes every row; you get only the file's path.

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

Input Schema

NameRequiredDescriptionDefault
formatNocsv
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it re-executes the pull's stored SQL (so results may differ from the original run) and returns only a file path, not the data. That is exactly the kind of context annotations (readOnly=false, destructive=false, openWorld=false) cannot convey. It stops short of covering overwrite behavior or permissions for the target path.

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?

One sentence, front-loaded with the format options and followed by the execution semantics and return value. Every clause carries information; nothing is padding.

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 2-parameter tool with no output schema and zero schema coverage, the description covers formats, re-execution semantics, and the return shape. Slightly incomplete on pull_id provenance and file-overwrite behavior.

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 description coverage is 0% with 2 params, so the description must carry the load. It usefully enumerates the allowed format values ('csv' or 'xlsx'), which the schema does not (no enums), but 'pull_id' is only implied by 'past pull' with no indication of where to obtain it.

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 and resource ('Export a past pull to a file on the user's machine') and scopes the output formats. It is clearly distinguishable from neighbors like save_pull or query, though it doesn't name a sibling to route against.

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?

The phrase 'past pull' implies this is for re-materializing an already-saved pull rather than running a new query, which gives implied usage context. However, there is no explicit when-to-use vs. when-not-to-use guidance and no named alternative for users who want the data in-app rather than on disk.

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