Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Check an export

argorant_export_status
Read-onlyIdempotent

Show how far one export has come and whether its file is ready to download. Use it with the job_id from argorant_create_export or argorant_export_list. For an export split into several files use argorant_export_batch_status, and to read a finished file here use argorant_download_export_preview. It is free, starts no new export and sends no email. 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_export_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe export's job_id, from argorant_create_export or argorant_export_list.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds genuinely new context — the call is free, starts no new export, and sends no email — which reassures an agent polling for status. It stops short of describing polling cadence or what the progress payload contains, keeping it at a 4 rather than a 5.

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?

The structure is front-loaded: purpose first, then parameter source, then sibling routing, then side-effect guarantees. Most sentences earn their place, but the docs anchor ('#reveal-enrich-export') does not match this tool's subject and the docs link could be attached more cleanly.

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 single-parameter status poll with an output schema and full annotations, nothing an agent needs is missing: purpose, input source, alternatives, and side-effect profile are all covered, and return values are handled by the output schema.

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 coverage is 100% and the schema already documents job_id with the same provenance note the description repeats. The description adds no format, range, or failure-mode detail for the parameter, so the baseline 3 is correct.

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 names a specific verb and resource: it reports how far a single export has progressed and whether its file is ready to download. That is clearly distinct from the sibling tools it references, so an agent can tell it apart from argorant_export_batch_status and argorant_download_export_preview 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?

It states the prerequisite (job_id from argorant_create_export or argorant_export_list) and explicitly routes the agent elsewhere for split exports and for reading a finished file. Both the when-to-use and the when-to-use-something-else conditions are spelled out.

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