Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Per diem fiscal years loaded

per_diem_fiscal_years
Read-onlyIdempotent

Which federal fiscal years of per diem rates are available, with their dates and standard rates. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only that dates and standard rates are included in the response, with no mention of ordering, current-year marking, or whether the list can be empty — modest added context on top of the annotations.

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

Conciseness3/5

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

The first sentence is compact, front-loaded, and tells the agent exactly what the tool returns. The second sentence is pure promotional boilerplate for the API provider's other products and does no work toward tool selection or invocation.

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

Completeness3/5

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

For a zero-parameter read-only list tool with no output schema, the description covers the return content at a coarse level (years, dates, standard rates) but says nothing about response shape, ordering, or how many years are typically returned. Complete enough to call, but not enough to predict the 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the input schema already states. The baseline of 4 applies, with no parameter-level insight needed or expected.

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?

It uses a clear declarative statement — 'Which federal fiscal years of per diem rates are available' — naming a specific resource (fiscal years) and the payload contents (dates and standard rates). It is distinguishable from siblings such as per_diem_rates or per_diem_locations, though it never explicitly says it is a discovery/reference list rather than a rate lookup.

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

Usage Guidelines2/5

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

No guidance is given about when to call this tool instead of per_diem_rates or per_diem_trip, and no statement that it is useful for discovering valid year values before querying other endpoints. The agent must infer the use case from the title and noun phrase alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources