ScorpTech x402 API

Pentanacci Mod

pentanacci_mod

Read-onlyIdempotent

P(n) mod m for the Pentanacci sequence. The modulus is a positive decimal integer, and zero is rejected. n runs from 0 to 4096. 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/pentanacci-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": "pentanacci_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?

Annotations already declare the operation as read-only, idempotent, open-world, and non-destructive. The description adds valuable context beyond annotations: a per-call price, an alternative HTTPS endpoint, and a guarantee that the returned residue is smaller than the modulus. It does not mention authentication or rate limits, but the added cost and access details are significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core formula, followed by parameter constraints, output guarantee, and pricing/endpoint. Every sentence contributes necessary information; no redundancy.

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 computational tool with no output schema, the description covers the operation, parameter constraints, output guarantee, and cost/access details. The only gap is that the Pentanacci sequence itself is not defined, but the name and sibling context likely suffice.

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?

With 0% schema description coverage, the description compensates by clarifying that mod must be a positive decimal integer and that zero is rejected—a constraint not fully captured by the schema pattern. It also restates the n range (0–4096), though that is already in the schema. It does not explain the 600-digit limit or that mod is passed as a string, but the added zero-rejection constraint is meaningful.

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 (P(n) mod m for the Pentanacci sequence) with a clear resource. It does not explicitly differentiate from sibling tools like pentanacci or pentanacci_sum, but the formula and name make the scope evident.

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 explicit guidance on when to use this tool versus alternatives such as pentanacci (raw term) or other mod sequence tools. The description only provides operational constraints (mod positivity, n range), leaving selection to inference.

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?