dof-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dof_daily_summaryA | Lists the publications in the Diario Oficial de la Federación for one day, with counts by edition and issuing organization. Use the returned ids with dof_get_note. Days without an issue (weekends, holidays) return total 0. |
| dof_get_noteA | Returns one DOF publication with its content as plain text. Long notes are paged: when nextOffset is present, call again with offset=nextOffset for the rest. |
| dof_get_indicatorsA | Returns indicators published in the DOF: FIX exchange rate (pesos per dollar), UDI value and TIIE rates. Without arguments, returns what SIDOF lists for today (on weekends and holidays that can be only the UDI). With date, the values published that day. With indicator, from and to, the daily series of one indicator (at most 366 days); prefer a series to find the most recent value of one indicator. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct object and action: a daily index of publications, a single publication's content, and economic indicators. The descriptions explicitly chain them ('Use the returned ids with dof_get_note') and clarify that indicators are a separate query mode, leaving no realistic misselection risk.
All three share a clear 'dof_' namespace, but two use the verb_get pattern (dof_get_note, dof_get_indicators) while the third is a noun phrase (dof_daily_summary). The deviation is minor and readable.
Three tools is at the thin end of a well-scoped set, but each covers a genuinely different need (index, document, series data) with no filler. It is slightly under-powered for a document-retrieval domain rather than over-scoped.
The core lifecycle (list a day, fetch a note with pagination, pull indicator series) is covered, but there is no way to search publications by keyword, organization, or date range across days, forcing agents to crawl day by day. That is a notable gap for a lookup service.