Skip to main content
Glama
Sign In
mcp-toolbox

mcp-toolbox

by jorgitobg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_boe_document

Retrieve a single bundled Spanish BOE document by identifier, returning its metadata and paragraphs for offline, read-only reading.

Instructions

Return one bundled BOE document (metadata + paragraphs) by identifier.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "get_boe_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the returned payload ('bundled... metadata + paragraphs'), which is real added value, but says nothing about behavior when the identifier is unknown, whether the bundle can be large, or any access constraints.

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?

One sentence, front-loaded with the action and resource, with zero filler. Every clause (single document, bundled contents, identifier lookup) carries information.

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?

An output schema exists, so return values need not be explained, and the description still summarizes the payload. For a one-parameter fetch tool this is nearly complete, with the only gap being not-found or error behavior for an invalid identifier.

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?

The single doc_id parameter has 0% schema description coverage, so the description must compensate. 'By identifier' clarifies that the value is a document identifier rather than a title or query string, but adds nothing about format, source (e.g., where the id came from), or validity constraints.

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 ('Return one bundled BOE document') plus the payload shape (metadata + paragraphs) and the lookup key ('by identifier'). It implicitly contrasts with the sibling search_boe by being a single-document fetch, but never names that sibling explicitly, so it falls short of full differentiation.

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?

Usage is only implied: 'by identifier' signals you must already hold a doc_id, which suggests this follows a search_boe call, but the description never states when to use this versus search_boe or triage_tenders. No exclusions, prerequisites, or alternative routing are given.

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

Deploy Server

Other Tools