Search recent US presidential Executive Orders published in the Federal Register. Optionally filter by keyword and date. Returns EO number, signing/publication date, title and links.
| Name | Required | Description | Default |
|---|---|---|---|
| term | No | Optional keyword to search within executive orders. | |
| since | No | Only EOs published on/after this date (YYYY-MM-DD). | |
| per_page | No | Results to return (default 10, max 30). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses that the tool returns EO number, dates, title, and links, and implies a read-only search. However, it does not clarify what 'recent' means, whether results are paginated, or any limits beyond the schema's max per_page.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler: the first states the primary action and resource, the second summarizes filters and output. Every clause earns its place, and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the tool's core purpose, filters, and return fields, which is helpful given no output schema. However, it leaves gaps: no definition of 'recent' date range, no default behavior when filters are omitted, and no guidance on choosing this over the sibling 'search_documents' for broader Federal Register searches.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond echoing 'keyword' and 'date' filters already covered by the schema; it does not explain formats, defaults, or edge cases beyond what schema descriptions provide.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Search') and a clear resource ('US presidential Executive Orders published in the Federal Register'), and indicates the returned fields. It is distinct from the generic 'search_documents' sibling by targeting a specific document type, though it does not explicitly name sibling tools to differentiate them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: it is for searching recent executive orders, with optional keyword and date filters. It does not explicitly state when NOT to use it or point to alternatives, so it stops short of a 5, but the intended use case is not ambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: agency lookup, single-document retrieval, executive order search, recent document monitoring, and full-text search. The overlap between recent_documents and search_documents is minimal because one is explicitly for monitoring recent publications while the other is for topic-based search.
Tool names are all lowercase and multi-word names use snake_case, which is predictable. Minor deviations exist: 'document' is singular while other resource-oriented names are plural, and 'search_documents' is verb-led while the rest are noun phrases.
Five tools is an appropriate, focused scope for a Federal Register research server. Each tool covers a necessary capability without redundancy or bloat.
The tool surface covers the core workflow: discover documents via search or recent listings, retrieve full details by document number, filter by agency, and access executive orders. There are no obvious dead ends for the stated regulatory intelligence purpose.