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

Consulta Boletines Oficiales - Legislación consolidada

boe_borme_texto

Read-only

Retrieves BORME document text from its identifier: full Section 2 announcements, or, for Section 1, only a specified company's acts when you provide its name.

Instructions

Texto de un documento del BORME a partir de su identificador (el que devuelve boe_borme_buscar). Para un anuncio de la Sección Segunda (BORME-C-AAAA-N), el anuncio completo. Para un documento de la Sección Primera (BORME-A-AAAA-NNN-PP o BORME-B-..., una provincia entera en un día) exige "denominacion" y devuelve SOLO los actos de esa empresa, nunca el documento entero. No es legislación. Puede contener datos personales publicados para la publicidad mercantil: úsalos solo para esa finalidad. Da siempre "url_pdf" (única versión oficial) en cualquier cita.

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_borme_texto"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentificador del BORME: BORME-C-AAAA-N (anuncio) o BORME-A-AAAA-NNN-PP / BORME-B-AAAA-NNN-PP (actos de una provincia).
denominacionNoDenominación de la empresa. Obligatoria para documentos de la Sección Primera (A/B).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial context beyond them: Section One returns only the company's acts and 'nunca el documento entero' (a partial-result behavior an agent must know), plus the personal-data usage restriction and the instruction to always cite url_pdf as the sole official version. These are traits nothing in the structured fields conveys.

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?

Purpose and identifier source come first, then the two document cases, then the non-legislation exclusion and citation rule. Every clause carries distinct information — no filler or restatement of the title.

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 must cover returns, and it does so at the semantic level (full announcement vs. acts only, url_pdf present). It omits the shape of the returned payload (field names, whether text is chunked), which is a minor but real gap for a text-retrieval tool.

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 coverage is 100%, so the baseline is 3; the description still adds meaning by tying 'denominacion' to a concrete behavior (it selects one company's acts out of a whole-province document) and by linking 'id' to the identifier format returned by boe_borme_buscar. Not a full 5 since the id-format detail is already in the schema.

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?

States a specific verb and resource ('texto de un documento del BORME') and immediately names the sibling that produces the identifier (boe_borme_buscar). It also distinguishes the two document families (Sección Segunda full announcement vs. Sección Primera extracted acts) and explicitly excludes legislation, so the agent can tell it apart from the norm-text siblings without opening a schema.

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?

Gives clear context: use it with an id returned by boe_borme_buscar, and notes 'No es legislación', which routes away from the norm-text tools. It does not name the specific legislative siblings or state what to do if the id is unknown, but the usage conditions are explicit rather than implied.

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