Skip to main content
Glama
Sign In

capsulam

by es.capsulam
OverviewDiscussionsAdmin

Buscar en las cápsulas

buscar
Read-only

Busca en el archivo de las cápsulas (síntesis revisadas, entradas de sus fuentes, lecturas de fondo y, en la de normativa, el texto oficial de cada artículo, en español, y fichas de normas técnicas ISO y EN, que no incluyen su texto) por palabras. Las fuentes están casi todas en inglés: incluye en la consulta los términos en inglés y en español, y los nombres propios tal cual. Devuelve los resultados más relevantes con su fecha y su enlace.

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": {
      "consulta": "<consulta>"
    },
    "name": "buscar"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoCuántos resultados (10 por defecto).
capsulasNoNombres de cápsula; sin ella, todas las del acceso.
consultaYesPalabras que buscar, en inglés y en español.
recientesNoDar más peso a lo reciente (novedades).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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, and the description adds meaningful context: the content types searched, the caveat that ISO/EN technical standards do not include their full text, and the fact that results include date and link. It does not cover pagination or permission details, but with annotations that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and stays to three sentences with no filler. The long parenthetical in the first sentence is dense, but it earns its place by defining the archive contents.

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 search tool with full schema coverage, no output schema, and safety annotations, the description supplies the essential search scope, query guidance, and return shape. It could be stronger by routing agents away from sibling tools, but nothing critical for invocation is missing.

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%, so the schema already documents consulta, limite, capsulas, and recientes. The description adds guidance for constructing consulta, but does not add syntax or meaning for the other parameters beyond what the schema provides.

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: "Busca en el archivo de las cápsulas ... por palabras", and enumerates the content types covered. The purpose is clear, but it does not explicitly distinguish itself from sibling tools such as capsulas, novedades, or noticia.

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?

Gives useful query-construction guidance: include terms in both English and Spanish and keep proper names as-is, because sources are mostly in English. However, it does not state when to use this tool instead of siblings, nor does it provide exclusions or alternatives.

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