UK Data for Agents

executive_order_by_number

Read-onlyIdempotent

Looks up one US executive order by its EO number (for example 14148) and returns its title, signing and publication dates, Federal Register citation, president and official govinfo PDF. For anyone who sees an EO number in the news or a court filing and wants to know what it is, without guessing. Source: the Federal Register (FederalRegister.gov API), which covers orders published from 1994 onward; older orders are not found here. (cost: 1 credit)

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

Input Schema

Name	Required	Description	Default
`eo_number`	No	integer, required, executive order number, e.g. 14148

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description still adds substantive behavior: the 1994-onward coverage boundary and the explicit warning that older orders are not found, plus the upstream source and a credit cost. The coverage limitation is exactly the kind of failure mode an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb, resource, and return payload, then the use case, then the caveat and cost. Mostly efficient, though 'without guessing' is filler and the parenthetical cost tag could be tighter.

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?

No output schema exists, but the description compensates by enumerating the returned fields. With coverage limits, source, and cost all disclosed, an agent has everything needed to call this correctly and interpret a not-found result.

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% and the single parameter is already documented, so the schema does the heavy lifting. The description nonetheless anchors the expected input value with a concrete example (14148), which mildly reinforces format expectations beyond the structured field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Looks up one US executive order by its EO number') and then enumerates exactly what comes back: title, signing and publication dates, Federal Register citation, president, and PDF. An agent can distinguish this from sibling tools like federal_register_document without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete usage scenario ('sees an EO number in the news or a court filing'), which implicitly answers when to reach for this tool. It does not name an alternative or exclusion path, so it stops short of full when/when-not routing.

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

All UK Data for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?