ScorpTech x402 Tools

Loan Apr

loan_apr

Read-onlyIdempotent

True cost of a loan including fees: the US Truth in Lending APR (Regulation Z actuarial method) and the EU APRC (Consumer Credit Directive annual effective rate), plus the payment, amount financed, finance charge and total of payments for a level-payment loan. Handles origination fees and points paid upfront or rolled into the loan, a balloon payment, and weekly to annual payments. Compares the note rate with the real borrowing rate so offers can be ranked. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/loan-apr

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": {
      "amount": "<amount>",
      "ratePct": "<ratePct>",
      "termMonths": "<termMonths>"
    },
    "name": "loan_apr"
  }
}

Input Schema

Name	Required	Description
`fees`	No	Prepaid finance charges (origination, points, broker fees)
`amount`	Yes	Loan amount (principal before financed fees)
`points`	No	Discount points as % of the loan amount (added to fees)
`balloon`	No	Extra amount due with the last payment
`payment`	No	Use this payment instead of computing it
`ratePct`	Yes	Nominal annual note rate
`termMonths`	Yes
`feesFinanced`	No	true: fees are added to the loan balance; false: paid upfront / deducted from proceeds
`paymentsPerYear`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive behavior; the description adds valuable context beyond that, including $0.002 USDC per successful call, x402/Solana access, an HTTPS endpoint, and the Regulation Z / Consumer Credit Directive calculation methods. It does not discuss error behavior, but the pricing and computation context are substantive.

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?

Front-loads the core calculation and output metrics, then adds supported scenarios and access/pricing details. It is dense but well-structured, with little wasted text.

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

Completeness5/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 still names the key return metrics (APR/APRC, payment, amount financed, finance charge, total payments) and covers important input variants such as fees, points, balloons and payment frequency. That is enough for an agent to understand when and how to call it.

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 78%, so most parameters are already documented. The description clarifies that fees and points can be paid upfront or financed, that balloon payments are supported, and that payment frequency ranges from weekly to annual, but it adds little for amount, ratePct and termMonths, and the payment override is explained only in the schema.

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?

States a specific calculation: true cost of a loan including US APR, EU APRC, payment, amount financed, finance charge and total payments. It is clearly identifiable as an APR/APRC calculator, though it does not explicitly contrast itself with sibling tools such as loan_amortization.

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?

Gives a clear use case—ranking loan offers by comparing the note rate with the real borrowing rate—and notes supported variants including fees, points, balloon payments and weekly-to-annual payment frequencies. It lacks explicit when-not guidance or named alternatives.

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

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