Skip to main content
Glama

mireforma.net

Permisos e ICIO de un municipio

reforma_get_municipality
Read-onlyIdempotent

Renovation rules for a Spanish municipality (INE code): ICIO tax rate, permit fee, e-office, permit type, climate zone, with official sources.

Normativa de reforma de un municipio por código INE: tipo del ICIO 2026, tasa de licencia, sede electrónica, ley urbanística (licencia y declaración responsable) y de habitabilidad de su comunidad, zona climática del CTE, patrimonio protegido y reglas autonómicas y municipales del validador, con fuente. Lo que falta sale como «dato no localizado». Público, sin teléfonos ni correos.

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": {
      "ine": "<ine>"
    },
    "name": "reforma_get_municipality"
  }
}

Input Schema

NameRequiredDescriptionDefault
ineYesCódigo INE de 5 dígitos, p. ej. 08019

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, idempotentHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful behavioral context beyond that: results cite official sources, missing fields are reported as «dato no localizado», and the tool is public with no phone or email data. It does not describe response structure, but the annotations carry the safety profile.

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 content is front-loaded and organized around the returned fields, but the full description is repeated in English and Spanish, which doubles length without adding new information. The long enumeration is useful but makes the definition less concise than it could 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?

For a one-parameter lookup tool with no output schema, the description is largely complete: it covers the data returned, source attribution, fallback for missing data, and privacy boundaries. It does not specify the return structure, but with no output schema that is a minor gap.

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%, and the single parameter is already documented as a five-digit INE code with an example. The description reinforces that lookup is by INE code but adds no additional syntax or format detail beyond the schema, so the baseline of 3 is appropriate.

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 states a specific resource and enumerates the exact renovation-related data returned: ICIO rate, permit fee, e-office, permit type, climate zone, protected heritage, and regional/municipal rules. It is clear what the tool retrieves, though it does not explicitly contrast itself with sibling tools such as reforma_search_municipalities or reforma_validate_plan.

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 implied by the INE-code lookup and the list of returned municipal rules, but there is no explicit guidance on when to use this instead of searching municipalities or validating a plan. The fallback behavior for missing data is helpful, but alternative-tool routing is absent.

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