Skip to main content
Glama

BOE of the day

get_daily_summary
Read-only

List what Spain’s BOE published on a selected day, with links to official PDFs, and count items by section so filtered or paged results still show the full day.

Instructions

List what the BOE published on one day, with links to the official PDFs.

The answer always counts the items in every section, so a filtered or paged answer still shows what else that day holds. Sundays have no bulletin.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_daily_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoPublication date. Defaults to today in Spain.
limitNo
offsetNo
sectionsNoOnly these sections. 1: general provisions (new laws and regulations); 2A: appointments; 2B: public-sector jobs; 3: other provisions (grants, agreements); 4: courts; 5A: public procurement; 5B: other official notices; 5C: private notices; T: Constitutional Court. Defaults to all.
title_containsNoOnly items whose title has every one of these words. Case and accents are ignored.

Output Schema

NameRequiredDescriptionDefault
dateYes
itemsYes
issuesYesIssue numbers published that day. More than one means an extraordinary issue.
noticeNoBasado en datos de la Agencia Estatal Boletín Oficial del Estado (https://www.boe.es). Solo la versión electrónica firmada del BOE, en PDF, es oficial y auténtica.
sectionsYesEvery section of the day, with its size.
next_offsetNoPass it as offset to get the next page; null on the last page.
total_matchingYesItems that match the filters, before paging.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral value: results link to official PDFs, counts are always reported for every section even on filtered or paged calls, and Sundays are empty. It does not cover pagination limits or whether section counts reflect totals beyond the page.

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?

Three short sentences, front-loaded with the core action, then the non-obvious counting guarantee, then the Sunday edge case. No filler or repetition of the schema.

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 an output schema present and annotations covering the safety profile, the description need not explain return values, and it covers scope, the empty-day case, and the section-count behavior. Pagination semantics for limit/offset remain unaddressed and no sibling routing is given, leaving a modest gap for a 5-parameter listing tool.

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 60%, with date, sections and title_contains documented but limit and offset bare. The description compensates for the sections/limit/offset behavior with the claim that a filtered or paged answer still counts items in every section, which is genuine semantic value, but it adds nothing about the title_contains matching rules or offset behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List what the BOE published on one day') plus the payload shape ('links to the official PDFs'), which clearly distinguishes a daily digest from get_legislation or search_legislation. It stops short of naming or contrasting those siblings, so an agent must infer the boundary.

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?

The 'Sundays have no bulletin' note gives a useful when-not condition, and the one-day scope implies when to reach for it. But there is no explicit routing guidance against search_legislation for targeted lookups versus a full-day listing.

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