MCP-BOE

get_boe_summary_range

Fetch and aggregate Spanish BOE summaries for a date range (max 31 days). Get all publications in one call instead of daily requests, with optional section filter and result limit.

Instructions

Obtiene y agrega los sumarios del BOE para un rango de fechas. Permite ver todas las publicaciones de un período sin llamar a get_boe_summary día por día. Máximo 31 días de rango.

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": {
      "from_date": "<from_date>",
      "to_date": "<to_date>"
    },
    "name": "get_boe_summary_range"
  }
}

Input Schema

Name	Required	Description
`section`	No	Filtrar por sección del BOE (ej: '1', '2A', '3'). Omitir para todas.
`to_date`	Yes	Fecha de fin en formato AAAAMMDD o YYYY-MM-DD
`from_date`	Yes	Fecha de inicio en formato AAAAMMDD o YYYY-MM-DD
`max_items`	No	Límite total de documentos a devolver (default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds the 31-day range limit and mentions aggregation behavior, which is useful. However, it does not disclose output format, pagination, possible errors, or whether it is read-only. This is moderate transparency.

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 two concise sentences with no fluff. It front-loads the purpose and immediately follows with usage guidance and constraints. Every word earns its place.

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

Completeness3/5

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

The tool has no output schema and no annotations, so the description must cover more ground. It explains the main purpose, when to use it, and a key constraint, but it does not describe the return structure or how aggregation affects results. For a moderate-complexity tool with 4 parameters, this is adequate but not 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?

Schema description coverage is 100%, so baseline is 3. The description adds the valuable constraint of a maximum 31-day range, which is not present in the schema's parameter descriptions. It does not elaborate on section or max_items, but the added date-range constraint justifies a 4.

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+resource: 'obtiene y agrega los sumarios del BOE para un rango de fechas' clearly stating it gets and aggregates BOE summaries for a date range. It distinguishes itself from sibling get_boe_summary by explicitly mentioning it avoids day-by-day calls.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool: 'Permite ver todas las publicaciones de un período sin llamar a get_boe_summary día por día', naming the alternative tool and giving a clear use case. It also provides the constraint of a maximum 31-day range.

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