ScorpTech x402 API

Credit Payoff

credit_payoff

Read-onlyIdempotent

Credit-card and revolving-balance payoff in exact cents. Give a balance, an annual percentage rate, and a fixed payment (or a minimum that is the greater of a percent of the new balance and a floor). Returns the months to zero, total interest, total paid, and a yearly rollup. Interest each month is round-half-up of balance × APR / 12. The last payment is the remaining balance plus that month's interest. Refuses a payment that does not cover the interest. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/credit-payoff

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": {
      "balance": "<balance>",
      "ratePct": "<ratePct>"
    },
    "name": "credit_payoff"
  }
}

Input Schema

Name	Required	Description
`start`	No	First payment date YYYY-MM-DD. Later payments fall on the same day, clamped to the month end
`balance`	Yes	Current balance, decimal
`payment`	No	Fixed payment per month
`ratePct`	Yes	Annual percentage rate, e.g. 19.99
`minFloor`	No	Minimum payment floor used with minPercent, default 0
`minPercent`	No	Instead of a fixed payment: percent of the new balance (after interest)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: monthly rounding rule (round-half-up of balance × APR/12), last-payment rule, refusal when payment doesn't cover interest, and concrete return contents. It also discloses the pricing model ($0.002 USDC per successful call) and an HTTPS alternative — richly informative.

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 purpose and key mechanics, and each sentence carries information. The pricing/HTTPS sentence is functional but slightly tangential to invocation; overall efficient.

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?

No output schema, but the description enumerates the outputs (months to zero, total interest, total paid, yearly rollup) and the computation rules. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description earns above baseline by explaining the relationship the schema only implies: payment versus a minimum that is 'greater of a percent of the new balance and a floor', which clarifies how minPercent/minFloor interoperate.

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 verb+resource ('credit-card and revolving-balance payoff') in 'exact cents', which is clearly distinct from generic siblings like compound_interest or loan_amortization. However, it doesn't explicitly name a sibling or draw the boundary against loan tools.

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?

It outlines the required inputs and the payment-vs-minimum choice, giving implied usage context. But there's no explicit when/when-not guidance versus closely related tools such as loan_amortization, compound_interest, or loan_apr.

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?