List all 13 indexed open data portals with dataset counts. Catalan portals (Generalitat, Barcelona, Diba, AOC, Reus, Girona, FGC, Idescat, Renfe) + Spanish national sources with Catalonia focus (INE statistics, REE energy, SEPE employment, CNMC fuel prices). No parameters required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate safe, idempotent read-only behavior. The description adds context by specifying the exact number of portals (13), listing them, and noting the dataset counts, which helps set expectations beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main action. The second sentence adds useful scope details without unnecessary fluff. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple parameterless list tool with no output schema, the description fully covers what it does, what output to expect (dataset counts), and the geographic focus. Annotations cover safety, so nothing is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description confirms 'No parameters required,' which is consistent with the empty input schema. No additional parameter meaning is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'List all 13 indexed open data portals with dataset counts.' It clearly differentiates from sibling tools like get_dataset_info or search_datasets by focusing on the high-level portal list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it: when you need an overview of all indexed portals and their dataset counts. It doesn't explicitly mention alternatives or exclusions, but the context is clear given the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a unique purpose: search datasets, get metadata, list fields, list categories, list portals, query data, find related datasets, and search radio archives. There is no overlap between them, and the descriptions clearly distinguish when to use each.
Most tools follow a verb_noun pattern (get_, list_, query_, search_), but 'related_datasets' breaks the pattern as a noun phrase. This is a minor inconsistency in an otherwise predictable naming scheme.
With 8 tools, the set is well-scoped for a data catalog server. Each tool addresses a distinct need, and the count is neither too sparse nor overwhelming for effective agent use.
The tools cover the full spectrum of data discovery (search, categories, portals), inspection (metadata, fields), extraction (query), and exploration (related datasets). The additional radioteca search expands the domain without leaving gaps in the core open data workflow.