Skip to main content
Glama
suparse

Suparse MCP Server

Official
by suparse

Download Results

download_results

Fetch and save exports for Suparse document IDs directly to your local disk. Supports CSV, XLSX, Google Sheets, and JSON formats.

Instructions

Fetch an export for one or more Suparse document IDs and write it directly to local disk. Use this for CSV, XLSX, Google Sheets, and saved JSON files. Do not call fetch_json_results unless you intentionally need full JSON in the MCP response. If output_path is a directory, the API-provided filename is used inside that directory. If cleanup is needed, call delete_documents after this tool succeeds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatYesExport format to write to local disk. Use this tool for csv and xlsx.
api_urlNoOptional API base URL. Defaults to SUPARSE_API_URL or Suparse production API.
export_typeNoExport mode for csv, xlsx, and google_sheets. Defaults to unified.
output_pathNoOptional local output file path or existing directory. When omitted, writes to the current working directory using the API-provided or generated filename.
document_idsYesSuparse document IDs to export.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatYes
export_typeYes
output_pathYes
document_idsYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses disk writing, directory behavior for output_path, and cleanup. Lacks details on overwrite behavior, permissions, or error handling, but adequate for typical 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?

Three sentences, front-loaded with purpose, then usage and behavioral notes. No redundancy, every sentence adds value.

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 schema coverage and presence of output schema, the description covers main purpose, usage guidance, and key behavioral aspects. Slight gap in optional parameters like api_url and export_type, but schema handles them.

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 100%, so each parameter is documented. The description adds value by explaining output_path directory behavior and format use cases, but does not provide deep additional semantics beyond schema.

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 clearly states the tool fetches an export and writes to local disk, specifies formats (CSV, XLSX, Google Sheets, saved JSON), and distinguishes from sibling fetch_json_results.

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?

Explicitly advises when to use this tool versus fetch_json_results, mentions cleanup with delete_documents, and provides guidance on output_path behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suparse/suparse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server