ScorpTech x402 API

Champernowne Start

champernowne_start

Read-onlyIdempotent

The first Champernowne place occupied by the integer m. 1 starts at 1, 10 starts at 10, 11 starts at 12, and 100 starts at 190. m runs from 1 to 999999999999. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/champernowne-start

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": {
      "m": "<m>"
    },
    "name": "champernowne_start"
  }
}

Input Schema

Name	Required	Description	Default
`m`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds useful behavioral context beyond that: pricing is $0.001 USDC per successful call via x402 on Solana, and an HTTPS endpoint is provided. Return format is not described, but examples partially reveal it.

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?

Front-loaded with the core definition, followed by compact examples, range, pricing, and endpoint. It is appropriately sized and every sentence contributes useful information for calling or paying for the tool.

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 one-parameter math tool with no output schema and strong annotations, the description is nearly complete: purpose, examples, bounds, price, and endpoint are present. It could more explicitly state the return value (the starting position index) and distinguish itself from sibling Champernowne tools.

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 description coverage is 0%, so the description must carry parameter meaning. It identifies m as the integer input and gives the range 1 to 999999999999, plus worked examples that clarify the expected input-output relationship. The range duplicates the schema, but the examples add real semantic value.

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 the specific result: the first Champernowne place occupied by integer m, with concrete examples. It is clear what the tool computes, but it does not explicitly differentiate itself from sibling tools such as champernowne_place or champernowne_owner.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides input-output examples and the valid m range, but never states when to use this tool versus the related champernowne siblings nor any exclusions or prerequisites. Usage is only inferable from the examples.

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?