ScorpTech x402 Tools

Munchausen Sum

munchausen_sum

Read-onlyIdempotent

The sum of the digits of n each raised to itself, taking 0^0 as 1. 0 gives 1, 1 gives 1, 2 gives 4, 10 gives 2, 3435 gives 3435, and 438579088 gives 438579089. n runs from 0 to 9999999999. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/munchausen-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": "munchausen_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?

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower, and the description still adds real operational context: $0.001 USDC per successful call via x402 on Solana and a parallel HTTPS endpoint. It does not say what happens on payment failure or invalid input, which keeps it below 5.

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 edge case, worked examples, domain, and cost/transport in a dense run of sentences with no filler. The six-example list is long but each item disambiguates a real edge case (0^0, 10→2, the 3435 fixed point).

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 one-parameter arithmetic atom with no output schema, the description covers definition, edge case, worked outputs (which effectively convey the return value), domain, and payment model. Only error/payment-failure behavior is unspecified, a minor gap at this complexity.

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 must carry the parameter, and it does: it defines n as the integer fed into the digit-power computation, restates the 0–9999999999 domain, and anchors it with six worked input→output examples. The role of n is fully clear, though the domain restatement duplicates the schema's min/max.

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 precise verb+resource: it computes the sum of each digit of n raised to itself, with the 0^0=1 convention spelled out. That is unambiguous on its own. It never distinguishes itself from the near-identically named sibling `munchausen` (or `digit_power_sum`), which is the main clarity gap.

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 statement of when to use this versus `munchausen`, `digit_power_sum`, or `narcissistic`, nor any prerequisite or exclusion. The definition implies its own application, but with a sibling named `munchausen` an agent gets no guidance on routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScorpTech x402 Tools 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?