Skip to main content
Glama

Get Article

get_article
Read-onlyIdempotent

Retrieves the exact text of a Mexican federal law article as it stood on a chosen date, including DOF publication date, decree, and GitHub commit link.

Instructions

Exact text of one article as it stood on a date, with the DOF date and commit of the version, the decree(s) that version reflects, since when the article has this wording, and a link to the exact lines on GitHub at that commit.

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>",
      "article": "<article>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawYesLaw abbreviation or slug, e.g. 'LFT', 'CPEUM', 'lgsm'. See list_laws.
dateNoDate the text should reflect (YYYY-MM-DD, DD-MM-YYYY or 'hoy'). Returns the latest version published in the DOF on or before that day.hoy
articleYesArticle number as written in the law: '27', '1o', '3o. Bis', '15-A', '353-Ñ', '29-A Bis', '21 bis 1'. Extra words such as 'fracción IV' are ignored.

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 closed-world behavior, so the safety profile is covered. The description adds useful context about provenance (which decree a version reflects, since when the wording applied, GitHub permalink), but says nothing about failure modes for unknown laws, missing articles, or dates before the first publication — and much of the return-value detail overlaps with the existing output schema.

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?

A single front-loaded sentence that leads with the core action and then lists the returned evidence. It is dense but every clause maps to actual output content, with no filler or repetition.

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 a full output schema, complete parameter documentation and annotations, the description only needs to frame the retrieval model, which it does. The remaining gap is behavioral: no guidance on missing articles, invalid slugs, or date fallbacks beyond what the schema states.

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%, including format examples and the 'hoy' default, so the schema already carries parameter meaning. The description only restates the date semantics ("as it stood on a date") without adding anything the schema does not already say about law, article, or date handling.

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 uses a specific verb and resource ("Exact text of one article as it stood on a date") and enumerates the payload (DOF date, commit, reflecting decree(s), validity start, GitHub link), so the agent knows exactly what it retrieves. It does not name or contrast with siblings like article_history or diff_article, leaving the differentiation implicit rather than stated.

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 only implied: fetch the wording of a single article at a point in time. There is no explicit when-to-use versus when-not, no pointer to article_history for tracking changes or diff_article for comparisons, and no note about what happens when the article or law is not found.

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