Skip to main content
Glama

Unit facts

get_unit_facts
Read-only

The facts of one cadastral unit (a flat, house, shop, parking space): use, surfaces, floor and floor position, building, energy certificate (letter, kWh/m², CO₂), tourist licences, and with the scope unacasa.valuation the sale and rent estimates, the Catastro reference value and the yearly IBI estimate. include_parcel adds the facts of its parcel. 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": {
      "unit_ref": "<unit_ref>"
    },
    "name": "get_unit_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
groupsNounit, energy, valuation, and with include_parcel the parcel groups
unit_refYescadastral unit reference (20 characters, e.g. 8960309VK3786B0009XY)
include_parcelNoadd the facts of the unit's parcel (default false)

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 openWorldHint=false, so safety is covered; the description adds that the usable field set depends on the caller's scope and that results carry an attribution obligation ('name unacasa.es as the source and give the page link ... cite_as'). It says nothing about behavior for invalid or unknown unit_refs, partial data, or response size, which matters for an open-ended fact lookup.

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?

A single dense paragraph that front-loads the core payload list, then conditions (scope, include_parcel), then the citation rule. Nothing is redundant, though the long comma-separated enumeration makes it slightly harder to scan than a two-sentence split would be.

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 carries the return-value burden and does so by naming the fact categories, including the conditional valuation block. Remaining gaps are error/edge behavior and the undocumented fields parameter, which are modest for a read-only lookup tool.

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 75% and the schema already documents unit_ref, groups, and include_parcel; the description mostly restates the include_parcel behavior and the scope gating. The 'fields' array parameter is never mentioned in either place, and no guidance is given on choosing fields vs groups.

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 concrete verb and resource ('facts of one cadastral unit') and enumerates the payload an agent will receive (use, surfaces, floor, energy certificate, tourist licences, valuation figures). It also clarifies the unit type in parentheses and distinguishes itself from parcel retrieval via 'include_parcel adds the facts of its parcel', though it never names siblings like get_valuation or get_parcel_facts directly.

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?

Gives two real selection signals: valuation fields (sale/rent estimates, Catastro reference, IBI) only appear with the unacasa.valuation scope, and set include_parcel only when parcel facts are also wanted. What's missing is an explicit contrast with the sibling tools that also return parcel or valuation data.

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