ScorpTech x402 API

Wedderburn Split

wedderburn_split

Read-onlyIdempotent

The Wedderburn-Etherington split of n. cross is the sum of a(i)a(n-i) over the pairs below the middle, and middle is a(k)(a(k)+1)/2 when n = 2k and 0 when n is odd. n = 6 gives cross 5, middle 1, and value 6. n runs from 1 to 80. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/wedderburn-split

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": {
      "n": "<n>"
    },
    "name": "wedderburn_split"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds material context beyond annotations: the $0.001 USDC x402 cost, Solana payment rail, HTTPS endpoint, and n range. It does not detail payment/error mechanics, but this is substantial added behavioral context.

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 mathematical definition, then example, range, and access details. Dense but earns most sentences; could be slightly clearer, but no obvious filler.

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?

No output schema exists, so the description must convey return values; the n=6 example implies cross, middle, and value fields. Combined with formula, range, and payment details, it is mostly complete for a one-parameter computational tool, though it omits explicit return-shape and error behavior.

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?

Only one parameter n with 0% schema description coverage, so the description must compensate. It gives the range 1-80 and a worked example n=6, but the range merely repeats schema min/max and it does not clarify n beyond 'split of n'; some ambiguity remains.

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?

Defines the specific mathematical resource: the Wedderburn-Etherington split of n, including cross, middle, and value, with an n=6 example. However, it does not distinguish this from sibling tools such as wedderburn, wedderburn_sum, or wedderburn_mod, so it stops short of a 5.

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?

Gives only the input range and a worked example; it does not say when to choose this split tool over wedderburn, wedderburn_sum, or wedderburn_mod. No explicit when/when-not guidance is present.

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?