Skip to main content
Glama
Sign In

Verithic · official data by municipality

by io.github.veredamonte-glitch
OverviewDiscussionsAdmin

Search by budget · Buscar por presupuesto y minutos a Barcelona

buscar_por_presupuesto
Read-onlyIdempotent

Given a purchase budget, says how many square metres of used housing it buys in each municipality with a published price (budget / average price per m²), sorted from most to least space. Each municipality carries its public transport minutes to Plaça Catalunya (door to door, leaving 7–9am on a weekday) and, as before, its driving minutes. Can be limited by maximum public transport minutes, by maximum driving minutes and by county. It is a municipal average without taxes or purchase costs, not the price of a specific flat. — Con un presupuesto de compra, dice cuántos metros de vivienda usada da en cada municipio con precio publicado (presupuesto / precio medio del m²), ordenado de más a menos metros. Cada municipio trae sus minutos en transporte público a plaza Catalunya (puerta a puerta, saliendo de 7 a 9 en día laborable) y, como antes, sus minutos en coche. Se puede acotar por minutos máximos en transporte público, por minutos máximos en coche y por comarca. Es una media municipal sin impuestos ni gastos, no el precio de un piso concreto.

Input Schema

NameRequiredDescriptionDefault
limiteNoHow many municipalities to return (default 10). Cuántos municipios devolver.
comarcaNoFilter by county, e.g. “Maresme” or “Barcelonès” (optional). Filtrar por comarca.
languageNoResponse language: "es" (default) or "en". Idioma de la respuesta.es
presupuesto_eurYesPurchase budget in euros. Presupuesto de compra en euros.
max_minutos_coche_barcelonaNoMaximum driving minutes to Plaça Catalunya, without traffic (optional). Máximo de minutos en coche, sin tráfico.
max_minutos_transporte_publico_barcelonaNoMaximum minutes by public transport to Plaça Catalunya, door to door, leaving 7–9am on a weekday (optional). Towns with no useful service are excluded. Máximo de minutos en transporte público, puerta a puerta, saliendo de 7 a 9 en día laborable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_minutos_transporte_publico_barcelona
      Added value: +{
+  "description": "Maximum minutes by public transport to Plaça Catalunya, door to door, leaving 7–9am on a weekday (optional). Towns with no useful service are excluded. Máximo de minutos en transporte público, puerta a puerta, saliendo de 7 a 9 en día laborable.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description still adds real context: the figure is a municipal average excluding taxes and purchase costs, not a specific flat, and transport minutes are door-to-door departing 7–9am on a weekday. It omits pagination/rate behavior, but the data caveats are genuinely useful.

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 sentence is well front-loaded and dense with useful detail, but the entire description is then repeated verbatim in Spanish, roughly doubling its length. For an English-reading agent the second half is pure redundancy, which costs it points on conciseness.

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?

There is no output schema, so the description carries the return-shape burden, and it does so well: it says what each municipality carries (m², public transport minutes, driving minutes) and that results are sorted descending. What is missing is minor — it never states the maximum row cap of 25 or the budget floor/ceiling, though those live in the schema.

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 description coverage is 100%, so the schema already documents all six parameters, including the county filter and the two minute limits. The description restates these constraints and adds only marginal nuance (the no-taxes caveat, the door-to-door assumption), so baseline 3 is appropriate.

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: given a budget, compute the square metres of used housing each municipality buys, sorted most-to-least. The formula (budget / average price per m²) and the supplementary transport-minutes payload make the operation unmistakable and clearly distinct from generic sibling tools like buscar_municipios or comparar_municipios.

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 description explains what can be constrained (max public transport minutes, max driving minutes, county) but never says when to pick this tool over siblings such as comparar_municipios or ranking_por_perfil. Usage is implied by the operation rather than stated, so it meets the minimum-viable bar without routing guidance.

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