ScorpTech x402 Tools

Pentanacci

pentanacci

Read-onlyIdempotent

The nth Pentanacci number. P0 through P3 are 0, P4 is 1, and each later term is the sum of the previous five. P(10) is 31. An optional modulus reduces the term, and zero is rejected. n runs from 0 to 4096. Past 15 digits the value is a decimal string. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/pentanacci

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

Input Schema

Name	Required	Description	Default
`n`	Yes
`mod`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses output behavior (decimal string past 15 digits), a constraint (zero is rejected), the n range, pricing, and the equivalent HTTPS endpoint. These details materially help an agent understand the call’s behavior and cost.

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 sequence definition and example, then moves to constraints and operational details. It is mostly efficient, though it repeats the n range already present in the schema and appends pricing/URL context that is useful but not strictly invocation-critical.

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 mathematical lookup with rich annotations, the description covers the essential inputs, output representation, and cost/endpoint context. It is nearly complete, with minor gaps around explicit sibling routing and the exact semantics of modulus rejection.

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?

With 0% schema description coverage, the description partially compensates by explaining that mod is an optional modulus and that zero is rejected. However, the phrase 'zero is rejected' is ambiguous because n is also allowed to start at 0, and the mod string format is not further explained beyond the schema pattern.

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 clearly states that this tool returns the nth Pentanacci number and defines the sequence with an example. However, it does not explicitly distinguish this tool from nearby siblings such as pentanacci_index, pentanacci_mod, pentanacci_step, or pentanacci_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?

Usage is implied by the mathematical purpose and the n range, and the description notes an optional modulus behavior. It does not explicitly say when to use this tool instead of sibling tools like pentanacci_mod or pentanacci_sum, leaving routing 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 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?