Skip to main content
Glama

Create a burofax draft for review

create_burofax_draft

Renders supplied, user-approved letter text and postal addresses as an A4 PDF draft in Spanish or bilingual text. Both the sender and the recipient address must be in Spain; others are rejected before anything is stored. Returns the page count, the price of each delivery option and a private review URL. No letter is sent and no charge is made. Payment takes place separately on the review page. Government identification numbers are outside the supported inputs.

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": {
      "sender": "<sender>",
      "recipient": "<recipient>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "create_burofax_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe full letter body exactly as the user approved it, in Spanish (or bilingual). Separate paragraphs with a blank line. No address blocks, date or signature: those are added automatically.
cityNoCity for the dateline "En <city>, a <date>". Defaults to the sender's city.
optionNoDelivery option: "correos" (Burofax de Correos) or "notificados" (certified notification by a trusted third party, not Correos). Use the user's choice; if they have none, use "correos". They can switch on the review page.correos
senderYesWho sends the letter. Must be a postal address in Spain (the acuse de recibo goes back there). Printed top left and on the signature line.
subjectYesShort subject line, in Spanish, printed as "Asunto: …", e.g. "Reclamación de la fianza del contrato de alquiler".
recipientYesWho receives it. Must be a postal address in Spain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / recipient / properties / country
      Added value: +{
      +  "description": "Omit it, or \"España\". Only addresses in Spain are accepted; any other country is rejected.",
      +  "maxLength": 60,
      +  "type": "string"
      +}
    • changedInput schema / properties / sender / description
      Previous value: -"Who sends the letter. Printed top left and on the signature line."New value: +"Who sends the letter. Must be a postal address in Spain (the acuse de recibo goes back there). Printed top left and on the signature line."
    • changedInput schema / properties / sender / properties / country / description
      Previous value: -"Only if the sender lives outside Spain, e.g. \"United Kingdom\". Omit for Spain."New value: +"Omit it, or \"España\". Only addresses in Spain are accepted; any other country is rejected."
  2. 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"
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, non-destructive, non-idempotent, closed-world), the description discloses that nothing is persisted if validation fails, that no letter is sent and no charge occurs, that payment happens later on the review page, and that government ID numbers are unsupported. For a mutation-style tool this is unusually complete disclosure of side effects and their limits.

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?

Four tight sentences, front-loaded with what is produced and followed by eligibility, return values and side-effect disclaimers; there is no filler. The final sentence about government identification numbers is terse enough to be slightly ambiguous about whether it refers to letter content or address fields.

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 no output schema, the description carries the return contract itself: page count, price per delivery option, and a private review URL. Combined with the Spain-only rule and the no-send/no-charge guarantees, an agent has everything needed to call this correctly for a nested-object, 6-parameter tool.

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 the baseline is 3, but the description adds meaning the schema does not: the body must be exactly what the user approved, must be Spanish or bilingual, and must exclude address blocks, date and signature. It also flags that identification numbers are outside the supported inputs, which constrains content in a way no field description states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Renders supplied, user-approved letter text and postal addresses as an A4 PDF draft" gives a specific verb and resource, and the closing sentences (no letter sent, no charge made) make clear this is draft creation, not dispatch. It does not name a sibling, so an agent must infer the boundary with quote_burofax from the price-return mention alone.

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?

The description establishes a precondition (text must be user-approved) and a hard eligibility rule (both addresses must be in Spain or the call is rejected before anything is stored), which implies when to call. It never states when to use a sibling such as check_spanish_address or quote_burofax instead, and offers no explicit when-not guidance beyond the country restriction.

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