Skip to main content
Glama

Transitorios

transitorios
Read-onlyIdempotent

Retrieve transitory articles (entry into force, deadlines, repeals) of a Mexican law's original text or of one reform decree, as applicable on a chosen date.

Instructions

Transitory articles (entry into force, deadlines, repeals) of the original text of a law or of one reform decree, as kept at the end of the consolidated text.

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": {
      "law": "<law>"
    },
    "name": "transitorios"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawYesLaw abbreviation or slug, e.g. 'LFT', 'CPEUM', 'lgsm'. See list_laws.
dateNoRead them from the version applicable on this date.hoy
max_charsNoMaximum characters of text.
decree_dateNoDOF date of the reform decree whose transitorios you want. Omit it for the transitorios of the original text.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety and determinism profile is covered. The description adds one genuinely useful behavioral note -- the content is 'as kept at the end of the consolidated text' -- which tells the agent about provenance and that it reflects the consolidated version. It says nothing about truncation behavior for max_chars, what happens with an unknown decree_date, or the shape/size of the result.

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?

It is a single front-loaded sentence with no filler; the parenthetical enumeration of what transitorios cover is informative rather than padding. The trailing clause 'as kept at the end of the consolidated text' is slightly dense but earns its place by conveying provenance.

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?

With full schema coverage, an output schema handling return values, and annotations covering the read-only/idempotent profile, the description only needs to orient the agent, which it does. Minor residual gaps (truncation semantics, invalid decree_date handling) are acceptable at this level of structured support.

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 every parameter is already documented, and the baseline is a 3. The description's phrase 'of the original text of a law or of one reform decree' reinforces the decree_date semantics (omit for original text, supply for a decree) but largely restates what the schema already says. It adds no syntax, format, or edge-case detail beyond the schema.

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?

The description names a specific resource (transitory articles) and scopes it with a parenthetical of what those contain (entry into force, deadlines, repeals). It also distinguishes the two content modes -- transitorios of the original text versus those of a single reform decree -- which maps directly onto the decree_date parameter. It stops short of naming a sibling like get_article to draw the boundary explicitly.

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?

Usage is implied: an agent can infer this is the tool for transitory provisions rather than ordinary articles, and the original-vs-decree distinction hints at which mode to pick. There is no explicit statement of when to prefer this over get_article, article_history, or reforms, and no exclusion or prerequisite guidance.

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