ScorpTech x402 API

Multiplicative Persistence

multiplicative_persistence

Read-onlyIdempotent

Multiplicative persistence: how many times the decimal digits of n must be multiplied to reach a single digit, and that digit. 39 takes 3 steps and ends at 4. 10 ends at 0 in 1 step. n runs from 0 to 999999999999999. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/multiplicative-persistence

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

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 declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the cost ($0.001 USDC per successful call via x402 on Solana) and an alternate HTTPS endpoint, which materially affects how an agent invokes it.

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 definition followed by two short illustrative examples and the pricing/endpoint note; every sentence carries information. Slightly dense in the final sentence but no wasted prose.

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 adequately supplies the return semantics (step count plus terminal digit), the input domain, and access/pricing details. Complete enough for an agent to call this correctly without opening the schema.

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 schema only carries type and min/max. The description states the range 0 to 999999999999999 and that n is the number whose digits are multiplied, which mirrors rather than extends the schema. It does clarify the semantic role of n, so a baseline 3 is fair for a single well-bounded parameter.

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 the exact operation (how many digit multiplications until a single digit is reached, and the resulting digit) with two concrete worked examples (39 → 3 steps, ends at 4; 10 → 0 in 1 step). It is clearly distinguishable from siblings like additive_persistence by its definition, though it never names that sibling explicitly.

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?

Usage is only implied: the description defines the function and gives the valid input range, from which an agent can infer when the tool applies. There is no explicit statement of when to prefer this over additive_persistence or digital_root, and no exclusions.

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?