Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Read part of an export file

argorant_download_export_preview

Read the first part of a finished export file as plain CSV text, up to max_characters, to show or use rows in the chat. Use it once argorant_export_status says the file is ready; for the whole file, the user downloads it in Argorant. Nothing is hidden, so it shows names, emails and other contact details from the user's own export, and the text can stop in the middle of a row. It is free and starts no new export. More in the docs at https://docs.argorant.com/docs/agents/tools#reveal-enrich-export

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": {
      "job_id": "<job_id>"
    },
    "name": "argorant_download_export_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe export's job_id, once argorant_export_status says the file is ready.
max_charactersNoHow much text to return, 1,000 to 50,000 characters (default 20,000).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the response is unmasked PII from the user's own export ('shows names, emails and other contact details'), the text may be cut mid-row, and the call is free and spawns no new export. It does not reconcile why readOnlyHint is false for an operation that 'starts no new export', which is the one gap an agent might trip on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then precondition, then caveats, in a compact block with no filler sentences. The trailing documentation link is the only element that does not directly serve tool selection.

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?

For a two-parameter read with an output schema and annotations already present, the description covers everything an agent needs: readiness precondition, cost, PII exposure, truncation behavior, and the fallback for full files. Nothing material 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 both parameters are already documented, but the description still adds interpretive meaning: max_characters truncates raw text and can stop mid-row, so callers know the tail may be malformed CSV rather than a clean boundary. That is value beyond the schema, not a restatement of it.

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 ('Read the first part of a finished export file as plain CSV text, up to max_characters') and immediately delimits scope against the whole-file path ('for the whole file, the user downloads it in Argorant'). An agent can distinguish this from argorant_create_export and argorant_export_status without opening any schema.

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 an explicit precondition ('Use it once argorant_export_status says the file is ready') and an explicit alternative for the case it does not cover (whole file → user downloads in Argorant). Nothing about when to reach for this versus a sibling is left to inference.

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

All Argorant toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources