Skip to main content
Glama
Sign In

capsulam

by es.capsulam
OverviewDiscussionsAdmin

Leer un artículo de la normativa

articulo
Read-only

Un artículo, anexo o disposición entero, con su texto oficial vigente y su enlace. buscar devuelve trozos; esto devuelve el texto completo. Necesita acceso a la cápsula de normativa.

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": {
      "norma": "<norma>",
      "referencia": "<referencia>"
    },
    "name": "articulo"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeNoPara textos muy largos: el carácter desde el que seguir (el valor «siguiente» de la respuesta anterior).
normaYesria, nis2, rgpd, lopdgdd, ens, eni, ley39, ley40, rd817 o aesia (o su nombre corto, como «Reglamento de IA»).
referenciaYes«5», «artículo 4 bis», «anexo III» o «disposición adicional primera».

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real context beyond them: the returned content is the *current* official text plus a link, and the call requires access to the normativa capsule. Pagination behavior is left to the `desde` parameter rather than repeated here.

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: what it returns, how it differs from `buscar`, and the prerequisite. No padding, and the resource definition is 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?

With no output schema, the description does the necessary work by stating that the result is the full official text and its link, and it flags the capsule-access requirement. For a simple two-required-parameter read tool this is essentially sufficient, with only per-parameter guidance deferred to the schema.

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 each parameter documented including examples of accepted values, so the schema carries the semantic load. The description adds nothing about `norma`, `referencia` or `desde`; baseline 3 is appropriate when the schema is this complete.

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?

The description names the exact resource (a whole article, annex or provision) and its payload (current official text plus link). It explicitly separates this tool from the sibling `buscar`, which returns fragments, so an agent can pick between them without inspecting either 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?

It gives a clear selection rule: use this when you need the complete text, use `buscar` when fragments suffice. It also states the capsule-access prerequisite. It does not spell out a when-not case, but the contrast with the sibling covers the practical decision.

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

All capsulam toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources