ScorpTech x402 API

Digit Power Sum

digit_power_sum

Read-onlyIdempotent

The sum of the digits of n each raised to k. 0 to any k from 1 up is 0. 153 to the 3 is 153. 4150 to the 5 is 4150, and 4150 to the 4 is 882. n runs from 0 to 999999999999999 and k runs from 1 to 15. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/digit-power-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>",
      "k": "<k>"
    },
    "name": "digit_power_sum"
  }
}

Input Schema

Name	Required	Description	Default
`k`	Yes
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/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 behavior. The description adds useful operational context: pricing per successful call, x402/Solana payment mechanism, an HTTPS endpoint, and numeric domain limits, which goes beyond 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 operation and examples, then bounds, then payment/endpoint details. It is dense but every sentence contributes useful information, with only minor repetition of schema bounds.

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 examples and definition make clear that the result is the computed integer sum. Ranges, examples, pricing, and endpoint information cover what an agent needs to call it correctly; explicit return-type wording would make it complete.

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 the burden. It explains that n is the base number and k is the exponent applied to each digit, provides concrete examples including 0^k, and restates valid ranges, giving meaningful semantics beyond the bare 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?

States a specific mathematical operation: sum of each digit of n raised to k, with concrete examples. It clearly describes what is computed, though it does not name sibling tools like digit_sum or narcissistic to distinguish itself.

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?

Implies usage through examples and domain ranges but gives no explicit when-to-use guidance or alternatives. An agent can infer it is for digit-power-sum computations, but must decide on its own versus digit_sum (k=1) or related tools.

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?