Skip to main content
Glama

Poll a CSV export job

get_export
Read-onlyIdempotent

Status of one export job this account already queued. When the file is ready, returns downloadUrl and webExportsUrl (https://boardwalkai.com/exports). Does not return the CSV and does not write a file. Send the user to webExportsUrl to download it. Does not use credits. Works for planned-project and building permit exports alike (dataset says which).

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": {
      "exportJobId": "<exportJobId>"
    },
    "name": "get_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
exportJobIdYesFrom create_export or list_exports.

Output Schema

NameRequiredDescriptionDefault
statusNo
messageNo
downloadUrlNo
exportJobIdNo
webExportsUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantive context: it does not return the CSV, does not write a file, does not consume credits, and returns downloadUrl/webExportsUrl. Those are exactly the misconceptions an agent would otherwise form about an 'export' tool.

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?

Five short sentences, each carrying a distinct fact, with the core purpose front-loaded. The two negative statements (no CSV, no file write) are not padding — they preempt likely agent errors.

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 one-parameter polling tool with an output schema and full annotation coverage, the description supplies everything needed to call it and to act on the result. Minor gap: it does not indicate what a not-yet-ready job's status looks like beyond implying polling, though the output schema likely covers that.

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?

With one parameter at 100% schema coverage, the schema already documents exportJobId including its provenance. The description's 'job this account already queued' reinforces ownership scope but adds no format or validation detail beyond the schema, so the baseline 3 applies.

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: retrieve the status of a single, already-queued export job. The phrase 'this account already queued' separates it cleanly from create_export and create_permit_export, and 'dataset says which' shows it covers both export families without needing a separate tool.

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?

Implies the sequencing clearly: this is for jobs already queued, so an agent knows to call create_export/list_exports first (also reinforced in the schema's exportJobId description). It also gives downstream guidance to send the user to webExportsUrl. It stops short of explicitly naming an alternative tool or a when-not-to-use condition.

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.

Resources