ScorpTech x402 API

Thue Sum

thue_sum

Read-onlyIdempotent

The number of 1-bits in the Thue-Morse sequence from lo through hi inclusive. The sum from t(0) through t(7) is 4. lo must not pass hi. Each index runs from 0 to 1000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/thue-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": "thue_sum"
  }
}

Input Schema

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

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 cover read-only and idempotent behavior, but the description adds useful context beyond them: the cost per successful call, the x402/Solana payment requirement, the HTTPS endpoint, and the invalid-range constraint. It also states that the result is a number, which compensates for the lack of an output schema.

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?

The definition is front-loaded, with the core operation stated first and supporting details following in a compact sequence. The example, constraints, pricing, and endpoint all serve clear practical purposes without unnecessary repetition.

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?

For a simple two-parameter mathematical sum with no output schema, the description provides enough to call it correctly: operation, inclusive bounds, valid ordering, maximum index, payment information, and alternate HTTPS access.

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 defines lo and hi as inclusive sequence indices, specifies the allowed 0 to 1000000 range, and notes that lo must not exceed hi, adding meaningful semantics beyond the bare integer 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?

The description states a specific operation: summing 1-bits in the Thue-Morse sequence over an inclusive index range. It clearly identifies the resource and action, though it does not explicitly differentiate this from nearby siblings such as thue_morse, thue_prefix, or thue_weight.

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?

The inclusive range and the rule that lo must not pass hi imply usage, but the description does not explicitly say when to use this tool versus alternatives like thue_morse or thue_prefix. There are no exclusions or routing guidance.

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?