Skip to main content
Glama

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

Meals and incidentals breakdown

per_diem_meals_breakdown
Read-onlyIdempotent

How a GSA M&IE rate splits into breakfast, lunch, dinner and incidentals, and the 75% first/last-day amount. 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_meals_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
fyNoFiscal year (2026 or 2027).
rateNoOne tier (68, 74, 80, 86 or 92).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real domain context by explaining the meal split and the 75% first/last-day rule, which annotations cannot convey. However, both parameters are optional (0 required) and the description never says what happens when fy or rate is omitted — no defaults and no error behavior — which is a meaningful gap for a lookup tool.

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 a tight, front-loaded statement of purpose. The second sentence is pure promotional boilerplate with UTM tracking that gives an agent no operational value and dilutes the definition.

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?

There is no output schema, so the description must carry the return shape, and it does reasonably well by enumerating the meal categories and the 75% rule. What is missing is default behavior for the two optional parameters and any tie-in to the fiscal-year or rate-tier siblings, leaving the definition only marginally complete for a two-parameter lookup.

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?

Schema description coverage is 100%: fy is documented as fiscal year 2026 or 2027 and rate as one tier (68, 74, 80, 86, 92). The description adds nothing about these parameters and does not clarify defaults or which tier yields which split, so the baseline 3 applies.

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?

The description states a specific resource and operation: the breakdown of a GSA M&IE rate into breakfast, lunch, dinner and incidentals, plus the 75% first/last-day amount. It is clear what data comes back, but it never names or contrasts with sibling rate tools such as per_diem_rates, which also deal with GSA rates.

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?

There is no when-to-use guidance, no statement of prerequisites, and no pointer to an alternative tool. An agent must infer from the sibling names alone whether to call this or per_diem_rates, which the definition does nothing to resolve.

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