Skip to main content
Glama

Export flat data

export_get
Read-onlyIdempotent

Export stored flat data for backup or analysis as JSON with selected or all sections, or as CSV with one section, using limit and offset to page non-member records.

Instructions

Exports the stored data of the flat for backup or analysis. With format json (default) it returns the requested sections, or all of them when sections is omitted; with format csv it returns exactly one section (expenses when omitted) as { contentType, content }. Members are never paged; limit and offset page every other section. Use the specific list tools for everyday reads and this one only for bulk dumps. Read-only; limited to 20 exports per hour per member (error rate_limited).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows per section. Omit to return all rows. Members are never limited.
formatNoOutput format. json can hold several sections, csv exactly one.json
offsetNoRows to skip per section, for paging together with limit. Defaults to 0.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
sectionNoOnly for format csv: the one section to export. Defaults to expenses.
sectionsNoOnly for format json: the sections to include. Omit to export all sections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / format / description
      Added value: +"Output format. json can hold several sections, csv exactly one."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows per section. Omit to return all rows. Members are never limited."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip per section, for paging together with limit. Defaults to 0."
    • changedInput schema / properties / section / description
      Previous value: -"Only for format csv: the one section."New value: +"Only for format csv: the one section to export. Defaults to expenses."
    • changedInput schema / properties / sections / description
      Previous value: -"Only for format json: limit the export to these sections."New value: +"Only for format json: the sections to include. Omit to export all sections."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real context: a concrete rate limit of 20 exports per hour per member with the error code rate_limited, and the non-obvious exception that members are never paged while limit/offset apply to every other section. Return shape is sketched for csv ({contentType, content}) but not for json, a minor gap.

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?

A single compact paragraph, front-loaded with the purpose before format rules, paging caveats, and the rate limit. Every clause carries operational information; nothing is padding.

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?

With six optional parameters, no required fields, and no output schema, the description supplies what an agent would otherwise have to infer: default format, default section, multi-vs-single-section behavior, paging exception for members, and the rate-limit failure mode. Nothing essential to a correct call is missing.

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 coverage is 100%, so the baseline is 3; the description earns more by explaining the conditional relationship between format and sections/section (json accepts multiple, csv exactly one, defaulting to expenses) and by clarifying that members ignore limit/offset. It largely restates a few schema notes ("Members are never limited/paged") rather than adding new detail there.

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?

States a specific verb and resource ("Exports the stored data of the flat") plus the intent (backup or analysis), and explicitly distinguishes itself from the per-section list tools. An agent can tell immediately this is the bulk-dump path rather than a normal read.

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?

Gives explicit routing guidance: "Use the specific list tools for everyday reads and this one only for bulk dumps," and adds format-level rules (json = several sections or all when omitted; csv = exactly one section, defaulting to expenses). Both the when-to-use and the when-not-to-use case are covered.

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