Skip to main content
Glama

Find a parcel

find_parcel
Read-only

Find the cadastral reference (refcat) of the parcel at a Spanish address or at a WGS84 point.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
addressNostreet address in Spain, e.g. 'Calle de Ferraz 94, Madrid'
postal_codeNo
municipalityNomunicipality name or 5-digit INE code (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and a closed-world scope; the description usefully adds the geographic domain (Spain) and the coordinate system (WGS84), which the annotations do not. It does not disclose what happens when both an address and coordinates are given, what occurs on an ambiguous or unmatched address, or what the refcat format looks like.

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?

A single sentence that front-loads the output (refcat) and then the two input modes. No filler, no restatement of the title.

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?

With no output schema, the description correctly names what is returned (the cadastral reference) and covers both accepted input channels, which is most of what an agent needs. The remaining gap is that with zero required parameters it never states that exactly one of address or lat/lon must be supplied.

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 only 40%, so the description must carry weight; it partially does by clarifying that lat/lon are WGS84 coordinates and that address means a Spanish street address, which is not in the schema. It says nothing about postal_code or municipality, nor that lat/lon must be paired and mutually exclusive with address, leaving half the parameters undocumented.

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?

States a specific verb (Find) plus the exact resource and return value: the cadastral reference (refcat) of a parcel. The mention of Spain and of two input modes (address or WGS84 point) makes it distinguishable from generic siblings like find_place or search_fields, though it never explicitly contrasts itself with them.

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?

Implicitly conveys two usage modes — supply a Spanish address, or supply a coordinate pair — which is real guidance about how to invoke it. However, it gives no explicit when-to-use-vs-alternatives guidance (e.g. use find_place for addresses without a parcel lookup) and no exclusions or failure cases.

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