Skip to main content
Glama

MCPFax Agent Continuity

How far along is the fan-out

work_status
Idempotent

Turn a fan-out from a black box into something you can act on: how many items are pending, leased, done, failed and dead-lettered, the results collected so far, and every dead letter with the error that exhausted it. THIS IS WHAT LETS A PARENT PROCEED WITH 4 OF 5 instead of blocking on a straggler. Counts are produced by scanning the queue, not from counters that can drift. $0.002 ONLY when there is real progress — at least one completion, failure or dead letter — and only when the answer has changed since you last paid for it. An untouched queue charges nothing and says so. The counts are exact and never paged; the results and dead-letter ARRAYS are windowed at 50 rows each and hand you a page token when there is more, so every dead-lettered item is genuinely reachable rather than merely flagged as missing. Paging is free — you are charged per distinct progress state, not per page. Costs $0.002 USDC per call via x402 on Base, and ONLY when done + failed + dead_lettered >= 1, and this exact progress state has not been billed before; otherwise the same call returns the full answer and settles nothing. Authenticate with Authorization: Bearer , or pass agent_key as an argument if your host cannot set headers. Equivalent HTTP route: POST /v1/work/status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queue_idYesThe queue. Alias: job_id. Example: 'permit-batch-2026-08'.
agent_keyNoYour agent_secret, if your MCP host cannot set the Authorization header. Prefer the header.
dead_page_tokenNoOptional: the `next_dead_page_token` from a previous call, to read the next page of dead letters. Opaque — hand it back exactly as given. Omit for the first page. Example: 'x:item-0051'.
results_page_tokenNoOptional: the `next_results_page_token` from a previous call, to read the next page of results. Opaque — hand it back exactly as given. Omit for the first page. Example: 'c:00001754932100000:item-0051'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_key / examples
      Added value: +[
      +  "the agent_secret that register returned"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / dead_page_token / examples
      Added value: +[
      +  "x:item-0051"
      +]
    • addedInput schema / properties / queue_id / examples
      Added value: +[
      +  "permit-batch-2026-08"
      +]
    • addedInput schema / properties / results_page_token / examples
      Added value: +[
      +  "c:00001754932100000:item-0051"
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Reveals billing behavior, exact scanning-based counts, free paging, authentication requirements, and idempotent-like billing semantics far beyond what annotations provide. The description is consistent with annotations; charging aligns with readOnlyHint false and idempotentHint true.

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

Conciseness3/5

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

Front-loaded with the main value and packed with useful details, but the pricing condition is repeated twice and the all-caps sentence adds flavor rather than necessity. It could be tightened without losing meaning.

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?

No output schema exists, so the description correctly carries the burden of explaining result content: count categories, results, dead-letter errors, 50-row windows, page tokens, auth, and cost. An agent has enough information to invoke the tool and interpret its response.

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?

Input schema already documents all four parameters with descriptions and examples, so the baseline is 3. The description adds small context like free paging and opaque tokens, but most parameter meaning already lives in the 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?

States a specific verb and resource: report fan-out progress counts, collected results, and dead letters with errors. The phrase 'THIS IS WHAT LETS A PARENT PROCEED WITH 4 OF 5' makes the operational purpose concrete and distinguishes it from generic status tools.

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?

Gives an explicit when-to-use scenario: a parent should call this to continue with partial success instead of blocking on a straggler. It does not name alternatives or state when not to use, but the context is clear enough for an agent to select it correctly.

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