Skip to main content
Glama

Don of Debt Portfolio Tools

Judgment interest estimate (illustrative)

judgment_interest_estimate
Read-onlyIdempotent

[agencies] Illustrative simple-interest estimate of post-judgment interest. Computes automatically only for states whose fixed statutory rate was source-checked (CA, IL, MD, MO, NC, NY, OR, PA, RI, VA, and WA consumer debt). Every other state, variable-rate state, or federal judgment needs a user-supplied rate_override_pct and returns a warning. Cites the statute, source URL, and check date. Not an amount owed and not legal advice. Inputs: amount, dates, state, debt type only — no names or case numbers.

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": {
      "state": "<state>",
      "principal_usd": "<principal_usd>",
      "judgment_date": "<judgment_date>",
      "as_of_date": "<as_of_date>"
    },
    "name": "judgment_interest_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
paymentsNo
debt_typeNo
as_of_dateYesYYYY-MM-DD
judgment_dateYesYYYY-MM-DD
principal_usdYes
defendant_typeNoUsed for New York (CPLR 5004): consumer debt against a natural person accrues 2%, otherwise 9%.
rate_override_pctNoRequired for states without a source-checked fixed rate. Confirm the rate with the court record or counsel.

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
stateYes
noticeYes
statusYes
sourcesYes
audienceYes
warningsYes
debt_typeYes
next_stepYes
rate_ruleYes
scenariosYes
as_of_dateYes
disclaimerYes
educationalYes
judgment_dateYes
principal_usdYes
defendant_typeYes
judgment_noticeYes
not_an_amount_owedYes
input_aliases_appliedYes

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?

Beyond the readOnly/idempotent annotations, it discloses that out-of-scope inputs return a warning rather than a silent number, that output cites statute, source URL, and check date, and that it rejects identifying data. These are meaningful behavioral traits an agent cannot infer from the annotation set or schema.

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?

Four tight sentences, front-loaded with what it computes and its jurisdictional limit, followed by override behavior, output provenance, and disclaimers. Every clause carries information; nothing is redundant with the title or schema.

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?

An output schema and annotations already cover return shape and safety profile, so the description need only add scope and caveats, which it does well. Minor gap: no statement on how partial payments are applied to principal or on any rate differences driven by debt_type beyond the Washington and New York cases.

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?

With schema coverage at 50%, the description compensates by enumerating the input surface (amount, dates, state, debt type) and by explaining when rate_override_pct is mandatory and why it must be court-confirmed. It does not explain how the payments array or debt_type interacts with the computation, leaving one gap.

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 and resource (simple-interest estimate of post-judgment interest) and immediately scopes it by naming exactly which jurisdictions it can compute without assistance. The agent can distinguish it from siblings like collection_net_recovery_calc or judgment_state_facts from the description alone.

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 clear use conditions: automatic computation only for the enumerated fixed-rate states, and a required rate_override_pct for every other state, variable-rate state, or federal judgment. It also states what the tool is not (an amount owed, legal advice). It does not name a sibling alternative, so it falls just short of full when/when-not/alternatives routing.

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