Skip to main content
Glama

Biblioteca abierta de Cumplida

Leer un precedente

leer_precedente
Read-onlyIdempotent

Lee completo un precedente mexicano por su número, registro o clave («2a./J. 22/98», «registro 2031002»), con su vigencia, a quién obliga, su cita formal, su fuente oficial, lo que dice de otros criterios y lo que otros dicen de él. Léalo antes de citarlo; desde sigue el texto donde se cortó. Las relaciones propuestas sin validar salen rotuladas.

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

Input Schema

NameRequiredDescriptionDefault
desdeNoDesde qué carácter seguir el texto, cuando la respuesta anterior dijo `sigue_desde`.
referenciaYesEl número («2a./J. 22/98»), el registro («registro 2031002») o la clave («SJF:2031002»).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond them: the returned facets (vigencia, a quién obliga, cita formal, fuente oficial, cross-references in both directions) and the caveat that unvalidated proposed relations are labeled as such. With no output schema, this disclosure of return content is exactly what the description must supply.

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 identifier forms, then the usage rule, then the pagination note. Dense but each clause carries information; the enumeration of returned facets is long but justified given the absent output schema.

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?

For a two-parameter read tool with no output schema, the description covers what is returned, how to page through long text, and the reliability caveat on proposed relations. Nothing an agent needs to call it correctly 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 coverage is 100% and both parameters are documented there, including the `desde` continuation semantics and the identifier formats. The description restates the identifier examples and the continuation behavior but adds no syntax or format detail the schema lacks, so the baseline 3 applies.

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 (lee completo) and resource (un precedente mexicano) plus the three accepted identifier forms with examples, and enumerates what the response carries (vigencia, obligatoriedad, cita, fuente, relaciones). It does not explicitly name a sibling to contrast with, so differentiation from leer_disposicion or buscar_jurisprudencia is left implicit.

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 a clear usage rule — 'Léalo antes de citarlo' — which tells the agent this is the verification step before citing, and explains the `desde` continuation for truncated text. It stops short of stating when NOT to use it or naming the search/verification siblings as alternatives.

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