Skip to main content
Glama

M&IE meal breakdowns

get_mie_breakdowns
Read-onlyIdempotent

Return how daily M&IE totals break down into breakfast, lunch, dinner and incidental expenses, as in effect on the given date. The CONUS table breaks down the five standard CONUS M&IE tiers and is returned by default. Set region=oconus for the generic DTMO/DSSR M&IE total table. If date is not specified, today's breakdowns will be returned.

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

Input Schema

NameRequiredDescriptionDefault
dateNoThe day the rates must be in force, YYYY-MM-DD; today when omitted. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date.
totalNoFilter by daily M&IE total in USD
regionNoBreakdown table to return; defaults to CONUSconus
verification_urlNoIncluded by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Specific date in YYYY-MM-DD format"New value: +"The day the rates must be in force, YYYY-MM-DD; today when omitted. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date."
  2. Changed2 schema fields changed
    • changedInput schema / properties / verification_url / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / verification_url / description
      Previous value: -"If 'True', will include a verification url in the payload, pointing to the official government source. This is useful to crosscheck that the API returns the proper data and for auditing."New value: +"Included by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it."
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's added value is the default table selection and the today-when-omitted fallback, which are modest but real behavioral details; it says nothing about response size, tier ordering, or the verification_url side effect, which the schema covers instead.

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?

Three sentences, front-loaded with the core return shape followed by the region switch and the date fallback. Slight redundancy remains: the 'today when omitted' default is repeated from the date parameter description.

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, zero-required-parameter rate lookup with no output schema, the description explains what the returned table contains (four meal components, five CONUS tiers), the two region variants, and the date default. Combined with annotations and a fully documented schema, an agent has everything needed to call it correctly.

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%, so all four parameters are already documented, including the plan-limit date windows and the verification_url default. The description only reinforces region semantics and the date default, and it says nothing about the total filter parameter; baseline 3 applies when the schema carries the load.

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 uses a specific verb and resource ('Return how daily M&IE totals break down into breakfast, lunch, dinner and incidental expenses') and clarifies that it returns a breakdown table rather than a single per diem figure. It implicitly separates itself from per-diem total tools, but never names any sibling such as get_dtmo_perdiem_conus or get_perdiem_allowance, leaving the alternative-selection step partly to inference.

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 operating context: the CONUS table is returned by default, region=oconus selects the generic DTMO/DSSR total table, and omitting date means today. What is missing is any statement of when to prefer a sibling tool (e.g. a plain per diem lookup) over this breakdown.

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