Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Interest owed on a late government invoice

prompt_payment_interest
Read-onlyIdempotent

Interest a federal agency owes on a late invoice under the Prompt Payment Act at the current Treasury rate (simple daily interest, added to principal every 30 days), or, for a state, the state's prompt payment rule with the interest at a rate you supply. Use for government contractors waiting on agency payments.

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>",
      "days_late": "<days_late>",
      "jurisdiction": "<jurisdiction>"
    },
    "name": "prompt_payment_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesInvoice amount in dollars.
days_lateYesDays past the payment due date.
jurisdictionYes"federal" or a state name or code.
annual_rate_pctNoOptional: annual rate to use (needed for most states).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint false, so the safety profile is covered. The description adds genuine behavioral value by disclosing the computation method (simple daily interest, added to principal every 30 days) and the two rate regimes. It does not say where the "current Treasury rate" comes from (live fetch vs. embedded constant) or in what units/precision the result is expressed, which matters for a numeric calculation tool.

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?

One dense but front-loaded sentence: the resource and federal calculation lead, the state variant follows, and the intended audience closes it. The parenthetical carries real information rather than padding, and no sentence is redundant, though the sentence is long enough that an agent must parse a nested disjunction.

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?

With no output schema and four documented parameters, the description covers both jurisdiction modes, the rate requirement, and the compounding convention—enough to call the tool correctly. Remaining gaps are the source/staleness of the Treasury rate and the shape of the returned figure (total interest vs. breakdown), which an agent would want before relying on the number.

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 coverage is 100%, so the baseline is 3. The description still adds meaning by explaining that federal mode uses the current Treasury rate automatically while state mode uses "the interest at a rate you supply," clarifying the conditional relevance of annual_rate_pct beyond the schema's looser "needed for most states" note.

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 computation and resource: interest owed on a late invoice, with two clearly delineated modes (federal Prompt Payment Act at the current Treasury rate, or a state rule at a supplied rate). An agent can immediately tell this is a calculation tool rather than a rules-lookup sibling like get_state_factoring_rules, and the scope is narrowed to government contractors awaiting agency payments.

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 clause "Use for government contractors waiting on agency payments" gives a clear usage context, and the description implicitly signals that state jurisdictions require a rate the caller supplies. It stops short of naming alternatives or stating when-not to use it (e.g., non-government invoices, or pointing to get_state_factoring_rules for the underlying rule text), so it is clear context without explicit exclusions.

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