Skip to main content
Glama
Sign In
AEMET-MCP

AEMET-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_municipality_code

Search Spanish municipalities by name or province to retrieve their codes and provinces, with accent-insensitive and typo-tolerant matching.

Instructions

Search Spanish municipalities by name or province (accent-insensitive, typo-tolerant).

Args: nombre: Partial or approximate name of a municipality or province.

Returns: A list of matching municipalities with their codes and provinces.

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": {
      "nombre": "<nombre>"
    },
    "name": "search_municipality_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
nombreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses accent-insensitivity and typo-tolerance, but does not mention pagination, error behavior, or limitations. It is adequate but not thorough.

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

Conciseness5/5

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

The description is extremely concise, front-loading the purpose and using a clear Args/Returns structure. Every sentence adds value with no wasted words.

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?

Given no output schema, the description explains the return value as a 'list of matching municipalities with their codes and provinces,' which is sufficient for an agent to understand the tool's output. It could mention default behavior for unmatched queries but is otherwise complete.

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?

The schema has 0% description coverage, and the description provides meaningful semantics for the only parameter 'nombre': 'Partial or approximate name of a municipality or province.' This compensates well for the lack of schema description.

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?

The description clearly states the tool searches Spanish municipalities by name or province, and highlights accent-insensitive and typo-tolerant search. It is distinct from siblings which are weather/station/beach related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool vs alternatives, nor does it mention prerequisites or postconditions. While the context of siblings makes usage somewhat clear, explicit guidance is missing.

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

Deploy Server

Other Tools