Skip to main content
Glama
Sign In

Verithic · official data by municipality

by io.github.veredamonte-glitch
OverviewDiscussionsAdmin

Find municipalities · Buscar municipios

buscar_municipios
Read-onlyIdempotent

Finds municipalities by part of the name and/or county and returns their slug and page link, to use with the other tools. Does not return figures. — Busca municipios por parte del nombre y/o comarca y devuelve su slug y el enlace a la ficha, para usarlos con las otras herramientas. No devuelve cifras.

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
limiteNoHow many to return (default 10). Cuántos devolver.
comarcaNoCounty, e.g. “Maresme” (optional). Comarca.
consultaNoPart of the name (optional). Parte del nombre.
languageNoResponse language: "es" (default) or "en". Idioma de la respuesta.es

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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"
+}
  3. 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 readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: what the tool returns (slug plus page link) and a negative scope statement (no figures), which matters because there is no output schema.

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?

Content is front-loaded and the scope-exclusion sentence is well placed, but the entire description is duplicated in Spanish, roughly doubling length without adding information for the reader. It is defensible for a bilingual server but not maximally concise.

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 five optional parameters, no output schema, and full annotation coverage, the description supplies the two things that would otherwise be missing: the return shape (slug + page link) and the boundary against figure-returning tools. Only the routing decision against listar_municipios remains unaddressed.

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 all five parameters including the zona enum nuance and limite bounds are already documented in the schema. The description only restates that matching is by partial name/county, adding little beyond the field descriptions. Baseline 3 applies.

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 and resource (finds municipalities) plus the matching criteria (part of the name and/or county) and the returned fields (slug and page link). The clause 'Does not return figures' cleanly separates it from the analysis/price siblings, though it never distinguishes itself from the closest sibling, listar_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?

'to use with the other tools' implies a chaining/lookup role, and 'Does not return figures' implies when-not-to-use-it-for-data questions, but no alternative tool is named and no explicit condition for choosing search over listing is given. Usage is implied rather than stated.

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