Crypto, web, finance and app data tools

Loan & Mortgage Calculator

loan_calculator

Amortizing loan or mortgage: periodic payment, total interest, payoff date, effect of extra payments and a yearly or full payment schedule. Any payment frequency.

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": {
      "principal": "<principal>",
      "annual_rate_pct": "<annual_rate_pct>",
      "years": "<years>"
    },
    "name": "loan_calculator"
  }
}

Input Schema

Name	Required	Default
`years`	Yes
`schedule`	No	yearly
`principal`	Yes
`start_date`	No
`extra_payment`	No
`annual_rate_pct`	Yes
`payments_per_year`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the model handles amortizing loans, extra payments, payoff dates, and schedule granularity, but it does not state assumptions such as fixed rate, compounding convention, or whether the tool is purely a calculation with no side effects.

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?

A single dense sentence with no wasted words. The key capabilities are front-loaded and the list of outputs is easy to scan.

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 output schema exists, so return-value explanation is not required. However, with no annotations, zero schema description coverage, and seven parameters, the description does not fully cover assumptions or parameter semantics needed for confident invocation.

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 0%, so the description must compensate for seven parameters. It adds meaning for extra payments, schedule ('yearly or full'), and payment frequency ('Any payment frequency'), but leaves start_date and the exact units or interpretation of principal, annual_rate_pct, and years implicit. Partial compensation only.

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 identifies a specific domain (amortizing loan or mortgage) and the exact outputs it computes: periodic payment, total interest, payoff date, extra-payment impact, and payment schedule. It is clearly distinguishable from every 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 Guidelines3/5

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

The phrase 'Amortizing loan or mortgage' implies the appropriate use case and 'Any payment frequency' scopes it further, but there is no explicit when-to-use or when-not guidance and no sibling alternatives are named. Adequate but not instructive.

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

All Crypto, web, finance and app data tools 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?