ScorpTech x402 API

Fine Sum

fine_sum

Read-onlyIdempotent

The sum of Fine numbers from lo through hi inclusive. The sum from F(0) through F(6) is 85. lo must not pass hi. Each index runs from 0 to 80. Past 15 digits the value is a decimal string. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/fine-sum

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": {
      "lo": "<lo>",
      "hi": "<hi>"
    },
    "name": "fine_sum"
  }
}

Input Schema

Name	Required	Description	Default
`hi`	Yes
`lo`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only and idempotent behavior. The description adds valuable context: pricing ($0.001 USDC per successful call), x402 payment on Solana, an HTTPS alternative endpoint, and the return format for large values (decimal string past 15 digits). It could mention error or rate-limit behavior but is otherwise strong.

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 description is front-loaded with the core purpose, then follows with example, constraints, output format, and payment details. It is appropriately sized for a math tool with payment semantics, though the pricing/endpoint information could be slightly more structured.

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 simple two-parameter sum function with annotations covering safety, the description provides enough to call correctly: range semantics, bounds, output format for large integers, and authentication/payment details. The only minor gap is not defining what 'Fine numbers' are, but that is likely assumed domain knowledge.

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 0%, so the description must carry parameter meaning. It clarifies that lo and hi are inclusive range bounds, that lo must not exceed hi, and that both indices run from 0 to 80. This adequately compensates for the missing schema descriptions, though it could explicitly label lo as the start and hi as the end.

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?

The description states a specific verb+resource: 'sum of Fine numbers from lo through hi inclusive', which clearly distinguishes it from the sibling 'fine' tool that likely returns individual values. It does not explicitly name alternatives, but the purpose is unambiguous.

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 is implied by the range-sum framing, and constraints like 'lo must not pass hi' and index bounds are given. However, there is no explicit guidance on when to use this versus the sibling 'fine' tool or other sum tools, leaving the agent to infer.

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?