Skip to main content
Glama

export_table

Writes a table from an opened document to a CSV file in the working directory, creating a sidecar notes file when needed and avoiding overwrites unless confirmed.

Instructions

Write one table from a document already opened with read_document to a CSV file in the working directory (default ./mdfi-tables/-.csv, UTF-8 with a header row). The table id comes from the table's label in the page text, e.g. [table p13-t1 — …]. A table with notes gets a .notes.txt file beside the CSV; never overwrites unless overwrite=true. Only once the document is ready. Free: never charges.

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": {
      "document_id": "<document_id>",
      "table": "<table>"
    },
    "name": "export_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
tableYes
overwriteNo
document_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the default output location and filename pattern, encoding and header-row behavior, the sidecar .notes.txt file created when notes exist, the non-overwrite default with the overwrite=true escape hatch, and that the call is free of charge. The main remaining gap is failure behavior — what happens when the table id is invalid or the table is not yet parsed — which is not described.

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?

Four compact sentences, each front-loading the action and then the constraint that matters — destination, id format, side effects, readiness, cost. No sentence restates the tool name or wastes words on boilerplate.

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?

Given an output schema exists, return values need not be explained, and the description covers destination, naming, encoding, sidecar files, and overwrite safety. What is missing is edge-case behavior around an unresolvable table id or an unready document, which matters for a write-to-disk tool.

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 0%, so the description must compensate for four undocumented parameters, and it largely does: it gives the default path template for 'path', the format and provenance of the table id for 'table' (from the page-text label, e.g. [table p13-t1 — …]), and the semantics of 'overwrite'. 'document_id' is only implied through the read_document prerequisite rather than explained directly, which keeps this below a 5.

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 — writing one table from an already-opened document to a CSV file — and scopes it to a document previously opened with read_document. That scope statement cleanly separates it from the sibling readers read_document and read_pages, which produce the document rather than an export artifact.

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 states the prerequisite explicitly ('from a document already opened with read_document') and adds a gating condition ('Only once the document is ready'), which is enough for an agent to know when it may call this. It stops short of stating when-not to use it or naming any alternative export path, so it is clear context without explicit exclusions.

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

Deploy Server

Other Tools