site

Late payment calculator: interest and fixed compensation

calculate

Run the Late payment calculator: interest and fixed compensation calculator: Statutory interest rate (base rate plus 8%); Interest per day (£); Statutory interest to date (£); Fixed compensation, section 5A (£). Missing inputs fall back to their documented defaults.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Days the payment has been late
`debt`	No	Invoice amount still unpaid
`baseRate`	No	Bank of England base rate
`purchaser`	No	Who owes you the money	business
`extraCosts`	No	Reasonable recovery costs above the fixed sum

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It helpfully lists the calculated outputs and explains that omitted inputs use documented defaults, but it does not clarify side effects, error behavior, or whether the operation is read-only.

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?

The description is front-loaded and compact, using a single sentence with a semicolon-separated output list. There is slight redundancy in repeating 'calculator', but no meaningful waste.

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

Completeness3/5

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

The description covers the main calculated outputs and default behavior, which is useful given there is no output schema. However, it does not explain how inputs like purchaser or extraCosts affect the results, nor does it describe the response shape, leaving some gaps for a calculator with five optional parameters.

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 with defaults and ranges. The description reinforces default fallback behavior but adds no parameter-specific semantics beyond what the schema provides, making 3 the appropriate baseline.

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 states a specific action (run the late payment calculator) and names the domain outputs: statutory interest rate, interest per day, interest to date, and fixed compensation. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools such as calculator_describe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The instruction to 'Run the Late payment calculator' implies the usage context, and the note about missing inputs falling back to defaults gives practical guidance. However, it does not state when to use this tool versus alternatives like calculator_describe or submit_enquiry, nor does it provide exclusions.

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

All site tools Inspect

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

Need Help?