Skip to main content
Glama
Sign In

Verithic · official data by municipality

by io.github.veredamonte-glitch
OverviewDiscussionsAdmin

List all municipalities with chosen fields · Todas las poblaciones con los campos que pidas

listar_municipios
Read-onlyIdempotent

Returns every published municipality (no cap) with exactly the fields you ask for, optionally filtered by min/max on any numeric field, by county, and sorted. One call answers questions such as “which is the cheapest town within 35 minutes of Barcelona?”. Each value carries source, period and read date; a missing value is null with its reason, and towns with no value in a filtered field are listed apart, never estimated. Call it without fields to get the default fields and the list of available field keys. — Devuelve todas las poblaciones publicadas (sin tope) con los campos que pidas, con filtros mínimo/máximo sobre cualquier campo numérico, por comarca y ordenadas. Una sola llamada responde a «¿cuál es la población más barata a menos de 35 minutos de Barcelona?». Cada valor lleva fuente, periodo y fecha de lectura; lo que falta sale a null con su motivo, y las poblaciones sin valor en un campo filtrado se listan aparte, nunca se estiman. Sin campos devuelve los de por defecto y la lista de campos disponibles.

Input Schema

NameRequiredDescriptionDefault
zonaNoZone: bcn (default, published) or madrid (published: Madrid, every figure with source and date, missing values null with their reason). Zona.bcn
ordenNoSort order. Orden.asc
camposNoField keys to return, e.g. precio_m2_vivienda_usada_eur, minutos_coche_barcelona, viviendas_vacias_pct (Barcelona and Madrid); in Madrid also paro_registrado_media, afiliados_ss_residencia, estudios_superiores_pct, densidad_hab_km2, vecinos_0_14_pct, vecinos_65_mas_pct. Default: price per m², rent, driving minutes, centre-to-centre public transport minutes, IBI. Claves de los campos.
limiteNoOptional cap on rows; by default all matching towns are returned. Tope opcional; por defecto, todas.
comarcaNoCounty (optional). Comarca (opcional).
filtrosNoNumeric filters; all must hold. Filtros numéricos; todos a la vez.
languageNoResponse language: "es" (default) or "en". Idioma de la respuesta.es
ordenar_porNoField key to sort by. Clave del campo para ordenar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / campos / description
      Previous value: -"Field keys to return, e.g. precio_m2_vivienda_usada_eur, minutos_coche_barcelona, viviendas_vacias_pct (Barcelona and Madrid). Default: price per m², rent, driving minutes, centre-to-centre public transport minutes, IBI. Claves de los campos."New value: +"Field keys to return, e.g. precio_m2_vivienda_usada_eur, minutos_coche_barcelona, viviendas_vacias_pct (Barcelona and Madrid); in Madrid also paro_registrado_media, afiliados_ss_residencia, estudios_superiores_pct, densidad_hab_km2, vecinos_0_14_pct, vecinos_65_mas_pct. Default: price per m², rent, driving minutes, centre-to-centre public transport minutes, IBI. Claves de los campos."
  2. Changed1 schema field changed
    • changedInput schema / properties / campos / description
      Previous value: -"Field keys to return, e.g. precio_m2_vivienda_usada_eur, minutos_coche_barcelona. Default: price per m², rent, driving minutes, centre-to-centre public transport minutes, IBI. Claves de los campos."New value: +"Field keys to return, e.g. precio_m2_vivienda_usada_eur, minutos_coche_barcelona, viviendas_vacias_pct (Barcelona and Madrid). Default: price per m², rent, driving minutes, centre-to-centre public transport minutes, IBI. Claves de los campos."
  3. Changed1 schema field changed
    • changedInput schema / properties / campos / description
      Previous value: -"Field keys to return, e.g. precio_m2_vivienda_usada_eur, minutos_coche_barcelona. Default: price per m², rent, driving minutes, door-to-door public transport minutes, IBI. Claves de los campos."New value: +"Field keys to return, e.g. precio_m2_vivienda_usada_eur, minutos_coche_barcelona. Default: price per m², rent, driving minutes, centre-to-centre public transport minutes, IBI. Claves de los campos."
  4. Changed1 schema field changed
    • changedInput schema / properties / zona / description
      Previous value: -"Zone: bcn (default, published) or madrid (in preparation: only what the repository has read, every figure with source and date, missing values null with their reason). Zona."New value: +"Zone: bcn (default, published) or madrid (published: Madrid, every figure with source and date, missing values null with their reason). Zona."
  5. Changed1 schema field changed
    • addedInput schema / properties / zona
      Added value: +{
+  "default": "bcn",
+  "description": "Zone: bcn (default, published) or madrid (in preparation: only what the repository has read, every figure with source and date, missing values null with their reason). Zona.",
+  "enum": [
+    "bcn",
+    "madrid"
+  ],
+  "type": "string"
+}
  6. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantive traits beyond them: per-value provenance (source, period, read date), null-with-reason semantics, and that towns lacking a filtered field are listed separately and 'never estimated'. The 'no cap' note also clarifies pagination behavior.

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?

Core purpose and scope are front-loaded in the first sentence, and every sentence carries information. The bilingual duplication doubles the length but is justified by the audience; it is well-structured though somewhat long.

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?

There is no output schema, so the description carries the return-shape burden, and it does so: it explains that each value includes source, period and read date, how missing values appear, and how filtered-out towns are separated. Complete for an 8-parameter, no-required-params tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds the non-obvious no-fields default behavior (returns default fields plus the available field-key list) and reiterates that min/max filters apply to any numeric field and combine conjunctively. It goes modestly beyond the schema.

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?

States a specific verb and resource ('Returns every published municipality') with explicit scope ('no cap') and operation set (filter, sort, field selection). This distinguishes it from search-oriented siblings like buscar_municipios by emphasizing exhaustive retrieval without a cap.

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?

Provides a concrete triggering use case ('which is the cheapest town within 35 minutes of Barcelona?') and a procedural hint ('Call it without fields to get the default fields and the list of available field keys'). It does not, however, name alternatives or state when-not-to-use versus siblings like buscar_por_presupuesto or ranking_por_perfil.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Verithic · official data by municipality toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources