Skip to main content
Glama

Get burofax status

get_burofax_status
Read-onlyIdempotent

Returns the recorded status, dated timeline and available status or certificate links for an order reference, draft reference or review/status URL. Events can include draft creation, payment, operator acceptance, delivery and certificate availability. This read-only operation does not create or change a letter.

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": {
      "reference": "<reference>"
    },
    "name": "get_burofax_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesOrder reference (BFX-…) or draft reference, or the full review/status link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by naming the event types returned (draft creation, payment, operator acceptance, delivery, certificate availability), which tells the agent what the response body represents.

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?

Three sentences, front-loaded with the return content, then the event enumeration, then a safety reassurance. The final clause partly duplicates the readOnly annotation, but it is short and does real routing work.

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?

With one parameter, no output schema and full annotation coverage, the description carries exactly the missing load: it describes what the tool returns (status, dated timeline, certificate links) in place of an output schema. Nothing an agent needs to invoke it correctly is absent.

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 single 'reference' parameter is documented with the same three accepted forms (BFX-… order reference, draft reference, full review/status link) that the description lists. The description therefore repeats rather than extends 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 ('Returns the recorded status, dated timeline and available status or certificate links') and enumerates the accepted reference forms. The read-only framing plus the 'status' focus makes it distinguishable from create_burofax_draft and quote_burofax 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the closing clause 'does not create or change a letter' indirectly points creation work to create_burofax_draft, but no sibling is named and no explicit when-to-use condition is given. An agent can infer the intent, but the routing is not spelled out.

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