Skip to main content
Glama

Quote a burofax

quote_burofax
Read-onlyIdempotent

Returns all-in EUR prices and inclusions for two delivery options between postal addresses in Spain (sender and recipient): a Correos burofax with acuse de recibo and copia certificada, and a certified notification by Notificados, a trusted third party distinct from Correos. Pricing uses the supplied page count, a character-count estimate, or one page by default. No draft, reservation or delivery is created.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quote_burofax"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoNumber of A4 pages, 1–10, if already known.
optionNoOption the user asked about, if any. Both options are always returned.
text_lengthNoLength of the letter body in characters, to estimate pages when the page count is unknown.

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.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — which it does by disclosing the page-estimation fallback chain and that no draft, reservation or delivery is created. It does not describe rate limits or the shape of the returned price data, so it falls short of 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?

Three sentences, front-loaded with the payload (both options and their inclusions) followed by pricing mechanics and the no-side-effects statement. The opening sentence is dense but every clause carries information; nothing is padded.

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?

For a 3-param, zero-required, read-only quoting tool with no output schema, the description covers the options, the pricing inputs and the absence of side effects. The only gap is that it does not sketch what the returned price/inclusions payload looks like, which matters slightly without an 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%, so the baseline is 3. The description does add genuine meaning by explaining the precedence of pages over text_length over the one-page default, but does not restate or enrich the pages range or the option enum beyond what the schema already says.

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 all-in EUR prices and inclusions for two named delivery options (Correos burofax vs. Notificados) between Spanish postal addresses. The closing clause 'No draft, reservation or delivery is created' cleanly separates it from the sibling create_burofax_draft.

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?

Makes the usage context clear: this is a pricing/inclusions lookup that stops short of creating anything, so it belongs before any draft step. It does not explicitly name create_burofax_draft as the alternative or state when-not to call it, keeping it below a 5.

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