ScorpTech x402 API

Pentanacci Sum

pentanacci_sum

Read-onlyIdempotent

The sum of Pentanacci numbers from lo through hi inclusive. The sum from P0 through P12 is 244. lo must not pass hi. Each index 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-sum

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": {
      "lo": "<lo>",
      "hi": "<hi>"
    },
    "name": "pentanacci_sum"
  }
}

Input Schema

Name	Required	Description	Default
`hi`	Yes
`lo`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: inclusive indexing, the lo <= hi constraint, the 0–4096 index bounds, the decimal-string output rule past 15 digits, and the per-call price. These are meaningful operational details not covered by the readOnly/idempotent/destructive annotations.

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?

The purpose is front-loaded in the first sentence, followed by constraints, output format, price, and an HTTPS alternative. Every sentence adds useful information for selecting or calling the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the key return behavior (sum, with decimal string past 15 digits), plus input constraints, example, pricing, and transport alternative. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 does so by explaining that lo and hi are inclusive Pentanacci indices, that each ranges from 0 to 4096, and that lo must not exceed hi.

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 operation and resource: the sum of Pentanacci numbers over an inclusive index range. It clearly distinguishes itself by being the range-sum variant rather than a term/index/mod/step tool, though it does not explicitly name any sibling.

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 'sum ... from lo through hi inclusive', which tells the agent this is for range-sum queries. However, there is no explicit guidance on when to choose this over pentanacci, pentanacci_index, pentanacci_step, or other related sibling tools.

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?