ScorpTech x402 API

Riordan Mod

riordan_mod

Read-onlyIdempotent

R(n) mod m for the Riordan numbers. The modulus is a positive decimal integer, and zero is rejected. n runs from 0 to 80. The residue is smaller than the modulus. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/riordan-mod

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>",
      "mod": "<mod>"
    },
    "name": "riordan_mod"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes
`mod`	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?

Beyond annotations that already mark this as read-only, idempotent, and non-destructive, the description adds useful operational context: pricing at $0.001 USDC per successful call, the x402/Solana payment mechanism, and an HTTPS alternative endpoint. It also states the output property that the residue is smaller than the modulus.

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 description is front-loaded with the core operation, then covers constraints, result property, pricing, and endpoint. It is efficient with no filler, though the pricing and URL details make it slightly longer than a minimal mathematical definition.

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 simple two-parameter mathematical tool, the description covers purpose, input constraints, output property, cost, and an alternate endpoint. It is nearly complete, with minor gaps around the modulus size limit and string representation.

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 parameter meaning. It explains that mod must be a positive decimal integer with zero rejected, which is important additional semantics, and restates the n range 0–80. However, it omits the 600-digit modulus limit and does not explain why mod is typed as a string.

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 specific computation: the residue of Riordan number R(n) modulo m. It clearly distinguishes itself from a plain Riordan-number lookup by naming the modulus operation, though it does not explicitly contrast with sibling tools like riordan or riordan_sum.

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 purpose and input constraints imply when the tool is applicable, but there is no explicit guidance on when to choose this over riordan, riordan_sum, or other modular tools. The n range and zero-rejection rule are stated, but alternatives are not mentioned.

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?