ScorpTech x402 API

Binary Partition Sum

binary_partition_sum

Read-onlyIdempotent

The sum of the binary partition numbers from b(0) through b(n). Through 0 it is 1, through 4 it is 10, through 10 it is 60, and through 20 it is 390. n runs from 0 to 1000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/binary-partition-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": {
      "n": "<n>"
    },
    "name": "binary_partition_sum"
  }
}

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?

The annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description focuses on additions: price ($0.001 USDC per successful call, x402 on Solana) and an HTTPS fallback endpoint. Pricing and payment-rail requirements are exactly the kind of operational context an agent cannot get from 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?

Front-loaded with the mathematical definition, then examples, then range, then commercial/logistics details. Every sentence is informative, with only minor redundancy between 'n runs from 0 to 1000' and the schema's minimum/maximum.

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, but the sample values effectively communicate return magnitude and type for a single-parameter math function, and pricing/transport details round out what an agent needs. The only gap is differentiation from the single-term `binary_partition` sibling.

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 carries the burden, and it does explain that n is the upper summation bound and that n runs from 0 to 1000. The worked examples (through 0→1, 4→10, 10→60, 20→390) give concrete semantic grounding beyond the bare min/max, though the range statement duplicates the 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 verb+resource: the cumulative sum of binary partition numbers from b(0) through b(n), which is meaningfully different from a single-term lookup. It never names the sibling `binary_partition`, so an agent must infer that the sibling returns only b(n) rather than the partial sum.

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?

There is no explicit when-to-use or when-not-to-use guidance, and the obvious alternative (`binary_partition`) is not mentioned at all. The only contextual hint is the n range 0-1000, which merely restates the schema bounds.

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?