ScorpTech x402 API

Moran Ratio

moran_ratio

Read-onlyIdempotent

n divided by its digit sum, when that division is exact. 18 gives 2, 21 gives 7, 12 gives 4, and 1 gives 1. A digit sum that does not divide n is rejected. n runs from 1 to 5000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/moran-ratio

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real value beyond them: explicit rejection semantics for non-dividing digit sums, the accepted input domain (1–5000), a stated price of $0.001 USDC per successful call via x402 on Solana, and an alternate HTTPS endpoint. Pricing and error behavior are exactly the kind of context annotations cannot carry.

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 core definition, then examples, then constraints, then payment/endpoint details. Three of the four examples are somewhat redundant, but each sentence otherwise carries operational information.

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 still conveys what is returned (the ratio, integer per the examples) and what happens on invalid input. Payment mechanics and the HTTPS alternative make it callable end-to-end; only sibling disambiguation is absent.

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?

Only one parameter (n) at 0% schema description coverage, but the description explains n through the formula ('n divided by its digit sum') and restates the 1–5000 bounds already present in the schema. It adds conceptual meaning but mostly duplicates min/max that the schema already encodes.

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 precisely: 'n divided by its digit sum, when that division is exact', backed by worked examples (18→2, 21→7). It does not, however, distinguish itself from sibling tools moran, moran_count, moran_next, moran_sum, which an agent must infer from names alone.

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?

No indication of when to choose this tool over moran_count/moran_next/moran_sum or any other arithmetic tool. The only quasi-guidance is the rejection rule ('A digit sum that does not divide n is rejected') and the range constraint, which are preconditions, not routing advice.

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?