ConstituChat: Constitución de Venezuela

Buscar artículos de la Constitución

buscar_articulos

Read-only

Busca en los 350 artículos de la Constitución de Venezuela (1999), con palabras clave o una pregunta en lenguaje natural, y devuelve los más relevantes con su título, un extracto y su URL. Úsala primero cuando no sepas el número del artículo; el extracto va recortado, así que para responder o citar lee después el artículo completo con leer_articulo. Solo lectura y sin clave, con un límite de consultas por minuto (HTTP 429 con Retry-After).

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

Input Schema

Name	Required	Description	Default
`limite`	No	Cuántos artículos devolver (1-20). Por defecto, 5.
`consulta`	Yes	Palabras clave o una pregunta en español, hasta 200 caracteres, p. ej. «derecho a la salud» o «¿quién puede ser presidente?».

Output Schema

Name	Required	Description	Default
`consulta`	Yes
`resultados`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

changedInput schema / properties / consulta / description

Previous value: -"Palabras clave o una pregunta en español, p. ej. «derecho a la salud» o «¿quién puede ser presidente?»."New value: +"Palabras clave o una pregunta en español, hasta 200 caracteres, p. ej. «derecho a la salud» o «¿quién puede ser presidente?»."

changedInput schema / properties / limite / description

Previous value: -"Cuántos artículos devolver (1-20)."New value: +"Cuántos artículos devolver (1-20). Por defecto, 5."

First observedOct 25, 2026

TDQS

A4.3/5.0

Behavior3/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 restates 'solo lectura'. It does add genuinely new operational context: no API key required, a per-minute rate limit, and HTTP 429 with Retry-After. However, it says nothing about pagination or ranking behavior. With annotations carrying the safety profile, a 3 is appropriate.

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 sentences, each doing distinct work: what it does, when to use it and what to do next, and operational constraints. The most decision-relevant routing advice is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still sketches the return payload (título, extracto, URL) and warns the extracto is truncated, which is exactly the caveat an agent needs before citing. No gaps for a 2-parameter read-only search tool.

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 coverage is 100%: both parameters document types, bounds (1-20, default 5) and the 200-character limit with examples. The description only restates 'palabras clave o una pregunta en lenguaje natural', adding no syntax or formatting detail beyond the schema, so baseline 3 applies.

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 ('Busca en los 350 artículos de la Constitución de Venezuela (1999)') with the accepted input forms and the return contents (título, extracto, URL). It clearly separates itself from the sibling leer_articulo by positioning itself as the discovery step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use it first when the article number is unknown, and instructs to follow up with leer_articulo for the full text when answering or citing. Both the when-to-use and the alternative are named.

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

All ConstituChat: Constitución de Venezuela tools Inspect

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

Need Help?