Skip to main content
Glama

AI Buildout Permits

Export

export
Read-only

A download link (valid 24 hours) for ledger rows with record dates, first-seen dates and source hashes: a CSV of events filtered by state, ticker, event type, start date or project, or the full ledger as Parquet files (events, projects, and every value each field has held with the days it was first and last seen). Requires a subscription.

Example questions:

  • "Export every Texas certification with first-seen dates as CSV"

  • "Give me the full ledger as Parquet for a backtest"

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

Input Schema

NameRequiredDescriptionDefault
sinceNo
stateNoTwo-letter US state code, e.g. TX, VA, OH.
formatNo
tickerNo
projectNo
event_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a safe, non-destructive, closed-world read, so the bar is lower. The description adds genuinely non-inferable behavior: the link expires after 24 hours, access requires a subscription, and the Parquet variant includes historical field values with first/last-seen days. The exact return shape (a URL string vs. inline data) is only implied by the phrase 'download link'.

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?

Front-loads the key fact (a 24-hour download link) and then the two output modes. The parenthetical enumeration of Parquet contents and the two example questions each earn their space by resolving real ambiguity. No filler or restated title.

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 six-parameter export tool with no output schema, the description covers access requirements, link lifetime, filter axes and the payload of each format, which is enough to call it correctly. Minor omissions are the date format for the start-date filter and whether an unfiltered CSV call is permitted (the description implies unfiltered means Parquet).

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 only 17% (only 'state' is documented), so the description has to compensate, and it largely does: state, ticker, event type, start date (since) and project are all named as filters, and the format parameter is covered by the CSV/Parquet distinction. Remaining ambiguity is the date syntax for 'since', which is not given as a format example.

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 concrete verb and resource: produces a download link for ledger rows, emitted either as a filtered CSV of events or as a full Parquet ledger. The two output modes and their contents are spelled out ('events, projects, and every value each field has held'), which makes it clearly distinct from query-style siblings such as find_projects or project_detail. It stops short of explicitly naming an alternative, keeping it just below a 5.

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?

The definition gives concrete usage contexts, including the two example questions showing a filtered CSV export and a full Parquet export for a backtest, plus the filter axes available (state, ticker, event type, start date, project). It also states the precondition 'Requires a subscription'. It does not say when to prefer a sibling tool over this one, which is the remaining gap.

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.