Skip to main content
Glama

opendata-cat

by io.github.xaviviro

search_radioteca

Read-onlyIdempotent

Search radio shows, episodes and people indexed at radioteca.cat (Catalan radio archive, ~485K documents from Catalunya Ràdio, RAC1, Catalunya Música, iCat, Catalunya Informació, RTVE, Cadena SER, ara.cat). Searches across episode titles, descriptions (which include a detailed summary of what was said), program name and subheading. Returns episodes (~473K), programs (~3K) and people (~9K). IMPORTANT: always cite radioteca.cat as the source and include the absolute 'url' in your reply for traceability — never paraphrase without linking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by document type.
yearNoFilter by year (4 digits, e.g. '2025'). NOTE: only year-level filtering is indexed; for a specific day, use the broader year filter and look at the URL path (radioteca URLs include /YYYY/MM/DD/) or the 'subheading' field which often contains the date.
limitNoMaximum results. Min 1, max 50. Default 10.
queryYesFree text in Catalan or Spanish. Searches title, description (contains episode summary), program and subheading. Examples: 'visita papa', 'eleccions municipals', 'crisi habitatge', 'Albert Serra cinema'.
offsetNoPagination offset. Default 0.
publisherNoFilter by broadcaster.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, and idempotent behavior. The description adds a crucial behavioral requirement: always cite radioteca.cat and include the absolute URL. It also explains that description fields contain summaries, which is useful beyond annotations. No contradiction detected.

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

Conciseness4/5

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

The description is moderately long but each sentence carries information: purpose, archive context, search scope, result counts, and the citation note. The broadcaster list adds context but is slightly verbose. Still, it is well-structured and front-loaded with the primary verb and resource.

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 no output schema, the description provides useful context such as result counts (episodes, programs, people) and mentions the absolute URL, which helps set expectations. It also notes that descriptions contain summaries, which is important for search behavior. While it doesn't detail pagination or output structure, those are partially covered by the schema, making it sufficiently complete.

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 coverage is 100% with all parameters described in detail. The description adds some context about what the query searches (titles, descriptions, program, subheading) but does not materially exceed the schema's parameter descriptions. 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?

The description uses a specific verb ('Search') and resource ('radio shows, episodes and people'), and clearly distinguishes this tool from generic dataset search siblings by naming the Catalan radio archive and its scope. It also identifies the specific search fields, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description implies this tool should be used for Catalan radio content queries by specifying the archive and content types, and the sibling tools are generic dataset searches. However, it does not explicitly state when not to use it or name alternatives, so it falls short of a 5.

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

All opendata-cat toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Resources