Skip to main content
Glama
Consulta Boletines Oficiales - Legislación consolidada

Consulta Boletines Oficiales - Legislación consolidada

boe_indice_norma

Read-only

Lists the blocks (articles, provisions, annexes) of a consolidated Spanish law with their IDs and titles so you can locate a specific article before requesting its full text.

Instructions

Índice de una norma consolidada: lista de bloques (artículos, disposiciones, anexos) con su identificador de bloque y su título. Úsalo para localizar el bloque de un artículo antes de pedir su texto.

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": {
      "id": "<id>"
    },
    "name": "boe_indice_norma"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentificador BOE-A-AAAA-N.
filtroNoFiltra los títulos que contengan este texto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and open-world, so safety is covered. The description adds genuinely new behavioral context by disclosing the shape of the return value (a list of blocks with identifiers and titles), which matters because there is no output schema. It says nothing about index size or pagination for very large norms.

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, zero waste. The definition of what is returned comes first and the workflow guidance second, both front-loaded.

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?

For a two-parameter read tool with no output schema, the description correctly compensates by explaining the returned block list. The only real gap is behavior for very long indices (pagination or truncation), which an agent would need to know before calling.

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%, with both 'id' (BOE-A-AAAA-N format) and 'filtro' documented in the schema itself. The description adds no detail beyond the schema about the identifier format or how 'filtro' matches titles, so baseline 3 applies.

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?

The description uses a specific verb+resource ('Índice de una norma consolidada') and states exactly what the result contains: blocks (artículos, disposiciones, anexos) with block id and title. It implicitly distinguishes itself from the text-fetching siblings ('antes de pedir su texto') but never names the alternative tool, so differentiation is inferential rather than explicit.

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?

It gives a clear usage condition: use this to locate an article's block before requesting its text, which establishes a two-step workflow. It does not say when to prefer boe_ficha_norma or boe_analisis_norma instead, so the exclusion side is missing.

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