Skip to main content
Glama
mjgmario

Spanish Public Data MCP

by mjgmario

search_recent_boe

Find recent Spanish BOE legislative publications by searching back up to 30 days. Filter by section and keywords to locate specific items.

Instructions

Search BOE publications from the last N days. Useful for finding recent legislative activity. Supports filtering by section and search terms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
days_backNoNumber of days to search back from today (1-30)
max_itemsNoMaximum total items to return across all days
search_termsNoSearch terms to filter items by title (case-insensitive, partial match)
section_filterNoFilter by section (e.g., '1', '2A', '2B', '3', '4', '5', 'T')
Behavior2/5

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

No annotations provided, description carries full burden. It does not disclose that tool is read-only, nor does it explain return format or pagination behavior. Merely restates filtering without additional behavioral context.

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?

Two sentences, no wasted words. First sentence states core functionality, second adds context and filtering. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and many siblings, description lacks details on output format, ordering, or how results are structured. Leaves agent guessing about return value.

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 parameters are well-documented. Description adds no new semantics beyond restating that filtering is supported.

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?

Description clearly states it searches BOE publications from last N days, with specific verb 'Search' and resource 'BOE publications'. It distinguishes from siblings like search_legislation by focusing on recent activity.

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?

Implies usage for recent legislative activity but does not explicitly state when not to use or provide alternatives such as get_boe_summary or search_legislation for different scopes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mjgmario/spanish-public-info-radar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server