Skip to main content
Glama
Sign In

mcp-server

by com.interzoid
OverviewDiscussionsAdmin

interzoid_irs_per_diem_rates

Read-onlyIdempotent

IRS per diem rates for any US location under the high-low method (Revenue Procedure 2019-48): classifies the location as high-cost or low-cost and returns the lodging and meals-and-incidentals (M&IE) amounts. For travel expense reimbursement, accountable plans, and expense management. Cost: $0.25 USDC via x402.

Input Schema

NameRequiredDescriptionDefault
lookupYesFull street address, ZIP code, city, county, or state (CONUS)
languageNoOptional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Optional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.",
+  "enum": [
+    "fr",
+    "de",
+    "it",
+    "es",
+    "ja",
+    "pt",
+    "zh",
+    "ar",
+    "nl",
+    "el",
+    "tr",
+    "ko",
+    "sv",
+    "vi",
+    "th",
+    "id"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / lookup / examples
      Added value: +[
+  "Manhattan, NY"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive. The description adds valuable context annotations can't carry: the pricing model ($0.25 USDC via x402, i.e., a paid call), the governing method (Revenue Procedure 2019-48), and what values are returned. It doesn't cover failure behavior for non-CONUS or ambiguous lookups.

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

Conciseness5/5

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

Two tight sentences: what it returns first, then use cases, then cost. Every sentence earns its place and the cost is front-loaded where the agent will see it.

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

Completeness4/5

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

Given no output schema, the description usefully says what comes back (high/low classification plus lodging and M&IE amounts) and discloses the paid-call cost. Minor gap: no mention that only CONUS locations are supported, which matters for invocation correctness.

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 coverage is 100% and both parameters are documented in the schema, including the enum and examples. The description adds no parameter-level detail beyond referencing 'any US location,' so the baseline 3 is appropriate.

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+resource: returns IRS per diem lodging and M&IE amounts for a US location under the high-low method. It names the classification outcome (high-cost vs low-cost) and cites Revenue Procedure 2019-48, distinguishing it clearly from siblings like sales_use_tax_rates or currency_rate.

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 use cases (travel expense reimbursement, accountable plans, expense management) that tell the agent when this tool applies. It doesn't explicitly exclude alternatives or warn about CONUS-only scope in the description — the CONUS restriction only appears in the schema — so it stops short of a 5.

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

All mcp-server toolsInspect
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