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

Consulta Boletines Oficiales - Legislación consolidada

boe_comprobar_atajos

Read-only

Verifies each frequent-legislation shortcut ID against the BOE and returns the official title it matches; run once after installation to confirm the shortcut table is correct.

Instructions

Auditoría interna: comprueba uno a uno los identificadores de la tabla de atajos de normas frecuentes contra el BOE y devuelve el título oficial que responde cada uno. Ejecútalo una vez tras instalar para confirmar que la tabla es correcta.

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": "boe_comprobar_atajos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that the check is performed 'uno a uno' against the BOE, implying a series of external calls (a real cost/latency signal), but says nothing about how many identifiers, failure handling, or what happens on mismatches.

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, front-loaded with the 'Auditoría interna' framing and then the per-identifier scope and return value, followed by the operational instruction. No filler.

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 zero-parameter, no-output-schema audit tool this covers purpose, trigger and result shape (official title per identifier). It could still say what the response looks like when an identifier fails to resolve or how many lookups to expect.

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?

Zero parameters, so the baseline of 4 applies. The description usefully clarifies that the identifiers come from the internal shortcuts table rather than from caller input, which pre-empts the natural 'what do I pass?' question.

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 concrete verb (comprueba/audita) and resource (tabla de atajos de normas frecuentes) plus the return value (título oficial). The 'Auditoría interna' qualifier clearly separates it from the verification siblings (boe_verificar_cita, boe_verificar_escrito), which check user-supplied citations rather than an internal table, though no sibling is named explicitly.

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?

'Ejecútelo una vez tras instalar para confirmar que la tabla es correcta' gives an explicit trigger and frequency (one-off, post-install). There is no explicit when-not guidance or named alternative for ongoing per-norma checks, which is the only gap.

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