UK Data for Agents

opm_status_history

Read-onlyIdempotent

When did OPM last close federal offices or allow early departure? Lists the US Office of Personnel Management's past operating status postings for the Washington, DC area, newest first: closures, delayed arrivals, early departures, unscheduled leave or telework days and lapses in appropriations, each with the date it applied to and when it was posted and replaced. Useful for HR, payroll and contractor questions. Ordinary open days are mostly not listed, and the online history covers recent years only. (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": "opm_status_history"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	integer, optional, number of postings to return, 1-100, default 20
`startrow`	No	integer, optional, how many of the newest postings to skip (for paging), default 0

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations, which already declare this a read-only, idempotent, non-destructive open-world lookup, the description adds useful behavior: newest-first ordering, DC-area scope, the types of postings included, each posting's applied/posted/replaced dates, and gaps in coverage for ordinary open days and older years. It also discloses the one-credit cost, though it does not describe response shape or pagination behavior in detail.

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?

The description is front-loaded with a concrete question and an explicit listing statement, then moves through examples, use cases, caveats, and cost. It is somewhat long for a simple two-parameter tool, but every sentence contributes to scope, usage, or limitations.

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?

For a read-only, two-optional-parameter tool with rich annotations and full schema descriptions, the definition covers what is listed, ordering, coverage limits, use cases, and cost. No output schema exists, but the description sufficiently characterizes the returned postings and their dates.

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?

The input schema fully documents both optional parameters, including types, ranges, defaults, and the paging purpose of startrow. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate for 100% schema description coverage.

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?

The description names a specific resource and scope: OPM's past operating-status postings for the Washington, DC area, with examples of closure types and newest-first ordering. The word 'past' and the opening question distinguish it from current-status siblings such as us_government_operating_status or us_shutdown_now.

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?

It gives clear use cases (HR, payroll and contractor questions) and important caveats: ordinary open days are mostly not listed and online history covers recent years only. It does not explicitly name an alternative tool for current status, but the history-versus-current framing makes the intended usage clear.

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?