Skip to main content
Glama

Clerk - IA Legal Dominicana

Leer una decisión de la Corte Interamericana

leer_sentencia_interamericana
Read-only

Una decisión de la Corte Interamericana por su clave. Sin modo, lo que DECIDIÓ: los puntos resolutivos y el mapa, que dice con su página dónde empiezan los ALEGATOS de la Comisión, del Estado o de los representantes, las CONSIDERACIONES de la Corte y los votos. Con modo: "buscar", los tramos donde aparece un término y de quién son. Con modo: "paginas", hasta diez páginas.

⚠️ El criterio de la Corte está en sus consideraciones: lo que va bajo «Alegatos» es de una parte, y un voto es de un juez. Se cita con la cita oficial y el párrafo («párr. 123»).

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": {
      "clave": "<clave>"
    },
    "name": "leer_sentencia_interamericana"
  }
}

Input Schema

NameRequiredDescriptionDefault
modoNodecision
claveYesLa `clave` de buscar_jurisprudencia_interamericana.
desdeNoModo «paginas»: primera página.
hastaNoModo «paginas»: última (como mucho diez).
buscarNoObligatorio en modo «buscar».
ventanaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds genuinely useful interpretive context: the Court's actual criterion lives in the consideraciones, text under «Alegatos» belongs to a party, and a voto belongs to a single judge, plus the citation convention with `cita` and paragraph. It does not cover failure behavior (e.g., missing `buscar`, out-of-range pages) or what the map/page output looks like structurally, so it stops short of 5.

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?

Front-loaded with the core action and then mode-by-mode behavior, followed by a bolded interpretive warning that is genuinely high-value rather than padding. The mode sentences are dense run-ons, and the warning's capitalization and quotes make it slightly harder to parse, but nothing is wasted.

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 six-parameter, three-mode reader with no output schema, the description does describe the return shape per mode (resolutive points, page map with where each section starts, term snippets, page text), which is the necessary compensation for a missing output schema. The undocumented `ventana` parameter and the absent 'get clave from the search tool first' instruction keep it from being complete.

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 67%, so baseline is 3. The description adds real meaning for `modo`, `buscar` and `paginas` (ten-page ceiling, who a term belongs to), but `ventana` is undocumented in both the schema and the description, and `desde`/`hasta` are only echoed from the schema rather than elaborated.

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 ('Una decisión de la Corte Interamericana por su clave') and then enumerates what each of the three modes returns: resolutive points and a page map, term occurrences with authorship, or up to ten pages. The resource is clearly distinguished from sibling readers such as leer_sentencia_colombia or leer_decision_francia by naming the Inter-American Court 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?

Gives explicit mode-selection guidance: no `modo` for what the Court decided plus the structural map, `modo: "buscar"` for term locations, `modo: "paginas"` for page ranges. The one gap is that it never states the upstream step — that `clave` must first come from buscar_jurisprudencia_interamericana — which is only present in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources