Skip to main content
Glama

Check a Spanish postal address

check_spanish_address
Read-onlyIdempotent

Checks the required fields of a Spanish postal address offline, the five-digit postcode range and the province indicated by the postcode. Returns normalised fields and a list of problems. Street existence and recipient identity are not verified. Addresses outside Spain are reported as a problem, because both the sender and the recipient must be in Spain.

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": "check_spanish_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoTown or city.
nameNoRecipient's full name or company name.
streetNoStreet, number, floor and door.
countryNoCountry, if the user gave one. Anything other than Spain is reported as a problem.
provinceNoProvince, if the user gave one.
postal_codeNoCódigo postal, 5 digits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Country, if the user gave one. Anything other than Spain is reported as a problem.",
      +  "maxLength": 60,
      +  "type": "string"
      +}
  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
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world behaviour, and the description adds genuinely new context: validation is offline, street existence and recipient identity are explicitly NOT verified, and the response shape is a normalised field set plus a problems list. Only the severity/shape of the problems list and any length limits on returned fields are left unspecified.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the capability and followed by the return contract and the explicit exclusions. Nothing is redundant with the title or the schema.

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 six-field, all-optional validator with no output schema, the definition supplies the return description, the negative guarantees, and the country constraint. An agent has everything needed to decide to call it and to interpret the result.

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 schema already defines each of the six fields, which sets the baseline at 3. The description adds a little meaning by tying country to the Spain-only rule and by linking province validation to the postcode, but it does not clarify that all parameters are optional or how partial input is handled.

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 opens with a specific verb and resource ("Checks ... a Spanish postal address") and enumerates exactly what is validated: required fields, five-digit postcode range, and postcode/province consistency. It also states the operation is offline, which cleanly separates it from the network-backed burofax siblings.

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 scope rules are clear (Spain-only, out-of-country input becomes a problem), which implies this is a pre-submission validation step, but the description never explicitly says when to call it or that it should precede create_burofax_draft. No alternatives are named, though the sibling set gives little ambiguity.

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