Skip to main content
Glama

Area or street facts

get_place_facts
Read-only

The figures of an area or a street of Spain, as on its unacasa page and in its CSV: population, age, income, declared and estimated rent, estimated values, the homes by kind and size, official price trend and sales (municipalities), cost of living, crime (Madrid districts), services, climate, elections ... Each row has id, label, value, unit, period and source; a street also lists its full building table (CSV/JSON link). When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

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

Input Schema

NameRequiredDescriptionDefault
langNo
pathNopath of the unacasa page, e.g. /madrid, /madrid/zona-malasana, /madrid/distrito-chamberi, /28006, /madrid/calle-alcala
place_idNoa place_id from find_place (municipality, district, neighbourhood, postal code)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior: row shape (id, label, value, unit, period, source), the extra building table returned for streets with CSV/JSON links, and a mandatory citation obligation. It does not cover failure modes for invalid paths or the effect of lang on the returned data.

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

Conciseness3/5

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

The core scope statement is front-loaded, but the long trailing enumeration with an ellipsis reads as filler rather than specification, and the citation instruction is mixed into the same block. It is serviceable but not tight.

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 does the necessary work of explaining the row structure and the street-specific building table, plus the citation requirement. Remaining gaps are minor: language effects, the path-vs-place_id relationship, and what happens when a place has no data.

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 67%, with path and place_id documented in the schema but lang undocumented. The description adds no parameter-level meaning, not even clarifying that path and place_id are alternatives or how language selection affects labels and sources.

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?

The description names the resource (figures for an area or street in Spain) and enumerates the concrete data domains returned: population, age, income, rents, home types, price trend, cost of living, climate, elections. It does not, however, distinguish this tool from siblings such as get_climate or get_valuation, which overlap with the listed outputs.

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?

Usage is only implied: the reader infers you call this for area/street statistics, and the place_id schema text points to find_place as the source of ids. There is no explicit statement of when to prefer this over get_valuation, get_climate or get_parcel_facts, and no note on whether path or place_id is preferable.

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