ScorpTech x402 API

Prorate

prorate

Read-onlyIdempotent

Prorate a money amount across a date range, in exact cents. The window is half-open: from the start date up to but not including the end date. The charge is amount × days used / days in the period, rounded half away from zero. The used range has to sit inside the period. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/prorate

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>",
      "periodStart": "<periodStart>",
      "periodEnd": "<periodEnd>",
      "useStart": "<useStart>",
      "useEnd": "<useEnd>"
    },
    "name": "prorate"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes
`useEnd`	Yes
`useStart`	Yes
`periodEnd`	Yes
`periodStart`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the rounding rule (half away from zero), the half-open interval semantics, the input-validation constraint, and a payment requirement ($0.001 USDC per successful call via x402 on Solana) — exactly the kind of auth/cost context annotations cannot express. It is fully consistent with readOnlyHint=true and idempotentHint=true.

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?

Four tight sentences, front-loaded with the operation and formula, followed by constraint then cost/access. No filler or restatement of the name.

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 deterministic pure calculation with no output schema, the description covers the math and validity constraints, but omits what the response contains (presumably the prorated amount in cents) and the input string formats. That leaves a modest gap an agent must guess at.

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 coverage is 0%, so the description carries the full burden; it does map every parameter into the formula (amount, period bounds, used range) and clarifies that amounts are exact cents. However it never states the date format implied by maxLength 10 (presumably YYYY-MM-DD) or whether amount is an integer string with no decimal point, leaving real ambiguity for a 5-required-param tool.

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?

States a specific verb and resource with its unit of precision: "Prorate a money amount across a date range, in exact cents." An agent can tell this apart from neighbors like day_count or invoice_total because the operation (time-proportional allocation) is named explicitly.

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 clear usage conditions: windows are half-open (start inclusive, end exclusive) and "the used range has to sit inside the period," which tells the agent when a call will be valid. It also names an alternative access channel (HTTPS GET endpoint) but never points to a sibling tool for related work, so exclusions/alternatives are only partial.

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?