Skip to main content
Glama

Search

search
Read-onlyIdempotent

Find words or phrases across Mexican federal law articles as they stood on a chosen date, optionally within one law, with ranked snippets and links.

Instructions

Full-text search over the articles of every law (or one law) as they stood on a date, ranked by number of hits, with a snippet and a link to each article.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawNoRestrict to one law (abbreviation or slug).
dateNoSearch the texts as they stood on this date (default: today).hoy
limitNoMaximum results.
queryYesWords to find (accent and case insensitive, each word is a prefix, all must appear in the same article). Use "quotes" for phrases and -word to exclude. Example: 'subcontrat "servicios especializados"'.
include_transitoriosNoAlso search the transitorios of the original text and decrees.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/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 profile is covered. The description still adds real behavioral context the annotations cannot: results are ranked by hit count and each carries a snippet and a link, and the corpus is a historical snapshot rather than the current text.

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?

A single well-built sentence with zero filler, leading with the verb and resource before adding ranking and return shape. Nothing needs trimming and nothing important is buried.

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 five parameters, a full schema, an output schema and read-only annotations, the description covers scope, date semantics and result shape adequately. It does not mention behavior when no articles match or the role of transitorios, but the schema handles those details.

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 the schema already documents query syntax, the law filter, the date default and the limit bounds. The description echoes the law narrowing and the date semantics but contributes no syntax or format detail beyond that, so 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?

The description names a specific verb and resource — 'full-text search over the articles of every law (or one law)' — and adds the point-in-time scope ('as they stood on a date'). That scope implicitly separates it from single-article siblings like get_article, but no sibling is named 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 only implied: the agent can infer this is the entry point when hunting for words across legislation, and the '(or one law)' aside hints at the law parameter narrowing. There is no explicit when-to-use/when-not guidance or routing to alternatives such as get_article or article_history.

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