ScorpTech x402 API

Loan Amortization

loan_amortization

Read-onlyIdempotent

Loan / mortgage amortization: periodic payment, total interest, payoff date and a yearly or full payment schedule (principal, interest, balance) for any rate, term and payment frequency (monthly, bi-weekly, weekly, quarterly, annual). Extra payments per period show months and interest saved. Fixed-rate, level-payment loans. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/loan-amortization

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>",
      "annualRatePct": "<annualRatePct>"
    },
    "name": "loan_amortization"
  }
}

Input Schema

Name	Required	Description	Default
`schedule`	No	Schedule detail (full is capped at 600 rows)	yearly
`principal`	Yes	Amount borrowed
`startDate`	No	First payment date YYYY-MM-DD (for payoff date)
`termYears`	No	Term in years (or use termMonths)
`termMonths`	No	Term in months
`extraPayment`	No	Extra principal paid every period
`annualRatePct`	Yes	Nominal annual interest rate in percent
`paymentsPerYear`	No	Payment frequency

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses two behaviors the annotations cannot: a per-call cost of $0.002 USDC via x402 on Solana, and an alternate HTTPS endpoint. It also states the fixed-rate/level-payment restriction, which is a real input constraint (not merely schema). It stops short of describing error behavior or whether unsupported loan types fail or are approximated.

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 computational capability is front-loaded, followed by limitations, then pricing/transport details. Dense but every clause carries information; the endpoint URL and price are arguably secondary but justified for a paid x402 tool.

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?

No output schema exists, so the description correctly enumerates the return values (payment, total interest, payoff date, schedule columns). It also flags the 600-row schedule cap and the fixed-rate assumption. The remaining gap is what a caller gets when term inputs are missing or contradictory, which the description leaves entirely to the schema.

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?

With 100% schema description coverage, the schema already documents all eight parameters, so baseline 3 applies. The description adds a little semantic value by enumerating the frequency options and by stating that extra payments report months and interest saved, but it does not explain the termYears vs termMonths interaction or what happens when neither is supplied.

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?

Names a specific computation (periodic payment, total interest, payoff date, amortization schedule) with its output columns, and scopes it to 'Fixed-rate, level-payment loans.' An agent can distinguish this from loan_apr / mortgage_affordability / credit_payoff on the basis of the stated deliverable alone.

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?

Usage context is implied by the scope line ('Fixed-rate, level-payment loans') and the frequency/extra-payment notes, but no sibling is named and no when-not condition is given. An agent must infer that loan_apr or mortgage_affordability cover the adjacent problems; nothing routes it explicitly.

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

All ScorpTech x402 API 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?