Skip to main content
Glama

curatedapi

Prompt Payment Act interest calculator

calc_payments_late_interest_us_prompt_payment
Read-only

The interest penalty a US federal agency owes on a late invoice under the Prompt Payment Act: the Treasury rate, compounded every 30 days on a 360-day year.

Uses the Prompt Payment rate in effect on the day after the due date for the whole delay. Unpaid interest is added to the principal at the end of each 30-day period, the leftover days earn simple interest on a 360-day year, and interest stops after one year. This is the Treasury formula P(1 + r/12)ⁿ(1 + r·d/360) − P.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "<amount>",
      "due_date": "<due_date>",
      "payment_date": "<payment_date>"
    },
    "name": "calc_payments_late_interest_us_prompt_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesThe unpaid amount (the invoice or debt). Allowed: > 0 and <= 1000000000000000. Unit: currency.
optionsNoPrecision and rounding of the results (default: rounding=half_even, decimals=2).
due_dateYesThe last day the payment was due (interest starts the day after).
payment_dateYesThe day the payment was or will be made (counted as a day of interest).
reference_rate_percentNoUse this Prompt Payment rate (in percent) for every day instead of the published one, for example for a date not yet covered. Allowed: >= -5 and <= 100. Unit: percent.

Output Schema

NameRequiredDescriptionDefault
inputsYesThe inputs as understood.
resultYes
formulaNo
receiptNoOnly with ?receipt=true: a signed receipt for this answer, a JSON Web Token signed with Ed25519 (alg EdDSA). Its claims are iss, iat, jti (the request id), endpoint, date and response (this response without the receipt). Check it with the keys at /.well-known/jwks.json or POST /v1/receipts/verify.
warningsYes
exactnessYesFor each decimal output: exact; rounded (correctly, to the precision); rounded_uncertified (the last digit could not be proven); or underflow (below 1e-100, reported as 0).
precisionNoThe precision and rounding that were applied.
calculatorYesThe calculator and version that ran.
referencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it is a safe, closed-world read, so the description carries the substantive burden and does so: it discloses the rate-selection rule (rate in effect the day after the due date, locked for the whole delay), the compounding cadence (every 30 days), the treatment of leftover days (simple interest, 360-day year), and a hard cutoff (interest stops after one year). Those are exactly the behavioral facts an agent cannot get from the annotations and which change the computed answer.

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?

It is dense and mostly front-loaded, with the jurisdiction and penalty framing first and the mechanics after. The final formula P(1 + r/12)ⁿ(1 + r·d/360) − P largely restates the preceding sentence in symbols, so one of the two could be trimmed without losing information.

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?

An output schema exists, so return values need not be described, and the description instead covers the non-obvious parts: the rate-timing rule, compounding period, day-count convention, and the one-year interest cutoff. For a five-parameter calculator with full schema coverage and annotations, nothing an agent needs in order to invoke it correctly is missing.

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?

Schema description coverage is already 100%, so per-parameter meaning is supplied there and the baseline is 3. The description earns an extra point by adding meaning the schema lacks: it explains how the rate is selected and applied over time (day-after-due-date rate held constant, 30-day compounding, 360-day year, one-year cap), which tells the agent how the amount/rate/date inputs actually combine. It does not mention the reference_rate_percent override or the rounding options, leaving that to the schema.

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 computation and a specific legal regime: 'The interest penalty a US federal agency owes on a late invoice under the Prompt Payment Act.' That verb+resource+scope combination immediately separates it from the sibling jurisdiction calculators (EU, Germany, UK, India MSME) without needing to open any schema.

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?

The applicability context is clear – US federal agency late-invoice penalties under the Prompt Payment Act – which implicitly excludes the non-US sibling tools. However, it never explicitly says 'use this instead of calc_payments_late_interest_eu when...' nor states any exclusion (e.g., non-federal or commercial invoices), so the routing is inferred rather than instructed.

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