Skip to main content
Glama

Biblioteca fiscal de Cumplida · edición abierta (gratuita)

¿Sigue vigente este criterio?

vigencia_de_un_criterio
Read-onlyIdempotent

Dice si un criterio mexicano sigue vigente, por su número, registro o clave: VIGENTE, AISLADA, SOBRESALIENTE, SUPERADA, INTERRUMPIDA o SUSPENDIDA, si sirve de apoyo y el criterio que lo superó o interrumpió, con su pasaje. Nunca afirme que algo está superado sin esto. Con sabido_al (AAAA-MM-DD), además, qué vigencia tenía según lo que la biblioteca sabía ese día y cada cambio desde entonces. [EN: Is this criterion still in force?.]

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": "vigencia_de_un_criterio"
  }
}

Input Schema

NameRequiredDescriptionDefault
sabido_alNoUn día (AAAA-MM-DD): además, qué vigencia tenía según lo que la biblioteca sabía ese día.
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. Changed1 schema field changed
    • addedInput schema / properties / sabido_al / description
      Added value: +"Un día (AAAA-MM-DD): además, qué vigencia tenía según lo que la biblioteca sabía ese día."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety bar is low; the description still earns credit by disclosing the returned taxonomy, that the response includes whether the criterion serves as support, and that it names the superseding/interrupting criterion together with its passage. It does not cover behavior when a reference is not found or ambiguous.

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?

Two sentences plus an English gloss, with the core verdict front-loaded and the conditional sabido_al behavior second. Little waste; the only slight redundancy is restating the sabido_al idea already present in the schema.

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?

There is no output schema, so the description must carry return-value semantics, which it does thoroughly (status values, support flag, superseding criterion plus passage, historical diff mode). It is nearly complete for a two-parameter read tool, with only not-found/ambiguity handling left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning: it clarifies that referencia accepts three identifier forms and that sabido_al is not just a date filter but a historical reconstruction — what validity the library knew that day plus every change since then, which the schema text omits.

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 — decides whether a Mexican criterion is still in force — and enumerates the exact outcome vocabulary (VIGENTE, AISLADA, SOBRESALIENTE, SUPERADA, INTERRUMPIDA, SUSPENDIDA), which pins down what the tool returns. It also lists the three accepted lookup keys (número, registro, clave). It does not explicitly distinguish itself from siblings such as verificar_citas or buscar_jurisprudencia, so it stops short of a 5.

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?

"Nunca afirme que algo está superado sin esto" is a direct, strong when-to-use mandate, and the second sentence explains the conditional case for adding sabido_al. There is no explicit when-not-to-use or named alternative tool to route to, so the guidance is clear but not exhaustive.

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