Skip to main content
Glama

Fox River Press

Work out a court payment plan

court_payment_plan
Read-onlyIdempotent

The arithmetic of paying a court fine or fee over time: give the amount owed and either a monthly payment or a number of months. Returns the number of payments, the last payment and the total. Courts set their own terms; this does not say what a court will accept.

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": {
      "owed": "<owed>"
    },
    "name": "court_payment_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
owedYesAmount owed, in dollars
monthsNoHow many months to pay over. Give this or monthly_payment.
setup_feeNoA one-time fee some courts add to a plan, in dollars
monthly_incomeNoOptional: monthly income, to show the payment as a share of it
monthly_paymentNoWhat can be paid each month, in dollars. Give this or months.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 goes beyond them by framing the tool as pure arithmetic whose output is not a legal determination, and by listing the returned values. It does not resolve what happens if both 'months' and 'monthly_payment' are supplied, or neither of the optional ones.

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 sentences, front-loaded with the operation and its required inputs, followed by the returned values and the scope caveat. No sentence is redundant and nothing is buried.

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, the description correctly compensates by naming the return values (number of payments, last payment, total). For a low-complexity, single-resource calculator that is nearly sufficient; only the conflict case for the two alternation parameters remains unaddressed.

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 the schema already documents all five parameters including the 'give this or months' alternation. The description's only added meaning is the same either/or framing and the note that courts set their own terms. Baseline 3 is appropriate; no syntax, rounding, or precedence detail is added.

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 names a specific operation on a specific resource: 'the arithmetic of paying a court fine or fee over time', and states the inputs it needs and the three values it returns. That is far more concrete than a restated title, though it never explicitly positions itself against any sibling tool.

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?

'Give the amount owed and either a monthly payment or a number of months' states the precondition for calling it, and 'this does not say what a court will accept' marks a clear out-of-scope boundary so the agent will not treat the result as authoritative. It stops short of naming when a different tool should be used instead.

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