Skip to main content
Glama

Parcel facts

get_parcel_facts
Read-only

The facts of a parcel (cadastre, building, land use, planning, terrain, hazards, infrastructure, proximity, energy, climate, soil, sunlight, valuation), each with value, unit, source, licence and status. Without fields / groups / preset: every field. When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

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": {
      "refcat": "<refcat>"
    },
    "name": "get_parcel_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNofield keys from list_fields; a key ending in * is a prefix
groupsNogroups: cadastre, building, land_use, farming, planning, terrain, hazards, infrastructure, proximity (incl. schools, health, shops, transport, parks), area (census section income, age, origin, households), location, energy, valuation, climate, soil, sunlight
presetNofarmland, buyer_home, climate, soil, hazards or building
refcatYescadastral reference of the parcel (14 characters, e.g. 8960309VK3786B)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), yet the description adds genuinely new behavioural information: each fact carries value, unit, source, licence and status, which reveals the response record shape in the absence of an output schema. It also imposes a licence-driven attribution obligation (cite unacasa.es and the page link via cite_as), a requirement an agent would otherwise miss.

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?

Front-loaded with the resource and the return shape, then the default behaviour, then the citation duty — a sensible priority order. The long parenthetical domain list is dense but each item is information the schema does not list under this key set, so it earns its space.

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 usefully explains the per-fact record structure and the default full-field behaviour, which is enough to call it correctly. Minor gaps remain: nothing about response size when all fields are returned, error behaviour for an invalid 14-character refcat, or how presets differ from groups.

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 enum-like lists of groups and presets are already documented in structured fields. The description only adds the semantics of omitting the three optional filters (returns every field), which is useful but thin beyond the baseline for a fully-described schema.

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+resource (facts of a parcel) and enumerates the twelve domains covered, so an agent knows exactly what comes back. It does not explicitly contrast itself with get_place_facts, get_unit_facts, or the narrower get_climate/get_soil/get_valuation siblings, so differentiation is only implicit in the word 'parcel'.

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 default behaviour is spelled out clearly ('Without fields / groups / preset: every field'), which tells the agent how to invoke it minimally. However, there is no guidance on when to prefer this tool over the more topical siblings such as get_climate or get_valuation, nor any stated prerequisites beyond having a refcat.

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