ScorpTech x402 API

Wedderburn

wedderburn

Read-onlyIdempotent

The nth Wedderburn-Etherington number. a(1) is 1, and a(1) through a(6) are 1, 1, 1, 2, 3, 6. Even and odd indices use the binary-tree split, with the middle term only on an even index. n runs from 1 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/wedderburn

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"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds concrete behavioral context beyond annotations: cost of $0.001 USDC per successful call, x402/Solana payment rail, decimal-string output past 15 digits, and an alternate HTTPS endpoint. It does not contradict the annotations.

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 definition is front-loaded with the core mathematical purpose and packs useful constraints, output format, price, and endpoint into a compact block. The binary-tree split detail is implementation-oriented and not strictly needed for invocation, but it is brief and does not bloat the description.

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?

With no output schema, the description still explains the return representation for larger values and implies numeric output otherwise. Annotations cover the safety profile, and the description includes range and pricing. It could additionally state the return type for small n or payment failure behavior, but it is nearly complete for a one-parameter read-only computation.

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 compensate for the single parameter. It explains that n is the sequence index, states the valid range 1 to 80, and notes the output representation change past 15 digits. It duplicates the schema's min/max but adds sequence meaning.

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 opens with 'The nth Wedderburn-Etherington number' and supplies initial sequence values, so the agent can tell it computes one term. It does not explicitly distinguish itself from siblings such as wedderburn_index, wedderburn_mod, wedderburn_split, or wedderburn_sum, so it falls short of full sibling differentiation.

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?

The description gives no explicit guidance on when to use this tool instead of the related wedderburn_* siblings. Usage is only implied by the 'nth ... number' phrasing; the range and pricing are constraints, not selection 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?