ScorpTech x402 API

Sociable Sum

sociable_sum

Read-onlyIdempotent

The sum of the aliquot cycle containing n. 6 gives 6, 220 gives 504, and 12496 gives 71056. A number that is not on a cycle is rejected. n runs from 1 to 20000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/sociable-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": "sociable_sum"
  }
}

Input Schema

Name	Required	Description	Default
`n`	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 safety, and the description adds real value beyond them: the rejection behavior for non-cycle inputs and the paid x402 model ($0.001 USDC per successful call, Solana, with an HTTPS mirror). It does not describe the return shape or what happens if payment fails, but nothing contradicts 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?

Front-loaded with the definition, then examples, then the rejection rule, then cost/transport. Each piece is short and useful in a paid-API marketplace; the pricing and URL sentence is long but operationally necessary here.

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 single-integer, no-output-schema math tool with read-only annotations, the description covers what is computed, the domain, the failure mode, and payment requirements. Only the sibling differentiation and return-value framing are missing, which is minor at this complexity.

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?

Schema description coverage is 0%, so the description must carry the parameter. It says 'n runs from 1 to 20000' and contextualizes n as a member of the aliquot cycle, which is helpful, but the range duplicates the schema's min/max and it never states whether n is validated against the cycle or merely a lookup key.

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 a specific computation on a specific resource: 'the sum of the aliquot cycle containing n'. The worked examples (6→6, 220→504, 12496→71056) pin down the exact semantics, which separates it in spirit from sociable_chain/sociable_length/sociable_min, though those siblings are never named.

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 precondition 'a number that is not on a cycle is rejected' is a genuinely useful usage constraint, and the range is stated. But there is no guidance on when to pick this over sociable, sociable_chain, sociable_length, or sociable_min, which is the main routing ambiguity for an agent in this family.

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?