Skip to main content
Glama

List Edition

list_edition
Read-onlyIdempotent

Lists the Mexican DOF table of contents for a given date, grouped by edition and issuing agency. Use it to browse official notices and get note codes, titles, pages, and links for full-text lookup.

Instructions

List the DOF table of contents for a day, grouped by edition and issuing agency.

Each note shows its code (use it with get_note), title, page and official link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_edition"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoPublication date: YYYY-MM-DD, DD-MM-YYYY, 'today' or 'yesterday'.today
editionNoWhich edition to list. 'all' lists every edition.all
include_avisosNoAlso list 'avisos judiciales y generales' (edictos, notices). They are numerous and usually noise, so they are hidden by default.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds the grouping shape and the note fields returned, but says nothing about behavior an agent would actually need — empty results on non-publication days, result volume, or pagination/limits on a busy day.

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, front-loaded with the resource and scope, then the follow-up action. Nothing is redundant and nothing 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 an output schema present and full parameter documentation, the description is close to sufficient for a read-only listing tool. The one real omission is what an agent should expect on days with no edition or on very large days, which affects how it should react to empty or long results.

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 the enum for edition and the rationale for hiding avisos by default, so the schema does the heavy lifting. The description adds only the loose notion of 'a day' for the date parameter and nothing on edition values or the avisos trade-off.

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?

A concrete verb and resource: 'List the DOF table of contents for a day, grouped by edition and issuing agency.' It tells an agent exactly what comes back (grouping) and links to a sibling via 'use it with get_note', but it never contrasts itself with search_notes for the case where the user wants a topic rather than a date.

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?

The second sentence implies a workflow: read a note's code here, then call get_note. That is genuinely useful routing. But there is no explicit when-to-use versus search_notes, and no mention of when to set include_avisos or which date formats are accepted at the tool level.

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