Skip to main content
Glama

Search Notes

search_notes
Read-onlyIdempotent

Search DOF note titles by keyword, date range, edition, or practice area, sorted newest first. Use it to find Mexican official publications when full-text search is unavailable.

Instructions

Search DOF note titles over a date range (up to 92 days per call), newest first.

SIDOF has no working full-text search, so this scans each day's table of contents. Results are cached, so refining a query over the same range is fast.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return.
queryNoKeywords matched against titles and issuing agencies, accent and case insensitive. Words are prefixes (eléctric matches eléctrica). Use "quotes" for phrases and | for alternatives, e.g. 'hidrocarburos | "gas natural"'. Optional when practice_area is given.
date_toNoEnd date (inclusive). Defaults to today.
editionNoRestrict to one edition.all
date_fromNoStart date (inclusive). Defaults to 30 days before date_to.
practice_areaNoPreset keyword set: ambiental, comercio_exterior, competencia, datos_personales, energia, financiero, fiscal, hidrocarburos, laboral, mineria, normas, telecom. Combined with query using AND when both are given.
include_avisosNoInclude avisos judiciales y generales (titles are usually codes).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover safety and idempotency (readOnlyHint, openWorldHint, idempotentHint); the description adds behavior the agent could not otherwise know. It discloses the critical limitation that matching is title-only because no full-text index works, that it works by scanning per-day tables of contents with a 92-day ceiling per call, that results are ordered newest first, and that range-level caching makes refinement cheap.

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?

Three short sentences with no filler. The capability and its hard limit are front-loaded, then the underlying mechanism, then the caching implication for iterative use, which is exactly the order an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven fully documented parameters, an output schema, and annotations covering safety, the description fills the remaining gaps that matter: title-only matching, the 92-day cap, ordering, and caching. Nothing needed to call the tool correctly appears to be missing.

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 is 3, and the description earns an increment by conveying constraints the schema does not: the 92-day maximum span between date_from and date_to and the newest-first result ordering. It still adds nothing about the query/practice_area interaction beyond what the schema's own parameter descriptions already spell out.

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 ('Search DOF note titles') and pins down scope with a date range, a 92-day cap, and 'newest first' ordering. It does not explicitly contrast with siblings like get_note or list_edition, so an agent must infer that this is the discovery tool and get_note is the retrieval tool.

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 context is implied rather than stated: 'SIDOF has no working full-text search, so this scans each day's table of contents' tells the agent how the tool behaves and implicitly that this is title-level discovery, and the caching note encourages iterative refinement. There is no explicit statement of when to prefer this over get_note or list_edition, nor any when-not guidance.

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