UK Data for Agents

loan_repayment

Read-onlyIdempotent

Monthly payment, total repaid and total interest on a personal, car or business loan at a given annual rate over a number of months or years. (cost: 1 credit)

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": "loan_repayment"
  }
}

Input Schema

Name	Required	Description
`years`	No	number (if months not given)
`amount`	No	number, required
`months`	No	number 1-600
`annualRatePercent`	No	number, required, e.g. 6.9

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world calculation. The description adds useful output content and a 1-credit cost, but it does not disclose key calculation assumptions such as fixed rate, amortization, fees, rounding, or currency.

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?

The definition is a single front-loaded sentence with the output set, loan types, rate, duration, and cost, with no redundant wording.

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?

For a simple read-only calculator with full schema coverage and no output schema, the description is nearly complete because it states the main returned values and credit cost. The main remaining gap is that it does not clarify assumptions or whether an amortization breakdown is returned.

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 all four parameters are already documented in the input schema. The description reinforces months-versus-years and annual rate, but adds little meaning beyond the schema and does not mention the amount parameter explicitly.

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 the concrete outputs (monthly payment, total repaid, total interest) and the resource: a personal, car or business loan over months or years at an annual rate. That scope also implicitly separates it from the sibling mortgage_repayment tool.

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 loan types imply when this tool applies rather than mortgage calculations, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent can infer usage, but the description does not route it actively.

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

All UK Data for Agents 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?