ScorpTech x402 API

Padovan Sum

padovan_sum

Read-onlyIdempotent

The sum of Padovan numbers, or Perrin numbers, from lo through hi inclusive. seq is p or r. lo must not pass hi. Each index runs from 0 to 8192. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/padovan-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": "padovan_sum"
  }
}

Input Schema

Name	Required	Default
`hi`	Yes
`lo`	Yes
`seq`	No	p

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds meaningful non-schema context: the index domain (0..8192), the invariant lo <= hi, a per-call price ($0.001 USDC, x402/Solana), and an alternate HTTPS endpoint. This price/payment disclosure is exactly the kind of behavioral detail annotations cannot convey.

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?

Purpose and range are front-loaded in the first sentence, with constraints and payment details following concisely. The HTTPS endpoint sentence is marginally useful but doesn't bloat the 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-required-parameter arithmetic tool with no output schema, the description covers the mathematical meaning, index bounds, validity constraint, and payment mechanics. It is largely complete, lacking only explicit sibling routing.

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?

Schema coverage is 0%, so the description must compensate; it explains that lo/hi are inclusive indices bounded at 8192, that lo must not pass hi, and that seq selects Padovan (p) or Perrin (r). It doesn't restate the default of seq or explain how large the returned sum can get, but it substantially compensates for the thin schema.

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?

It states a specific verb and resource: the sum of Padovan/Perrin numbers from lo through hi inclusive. The seq explanation (p vs r) clarifies that this single tool covers both sequences, but it doesn't explicitly differentiate itself from siblings like padovan, padovan_step, or perrin.

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?

'lo must not pass hi' is a validation constraint, not usage guidance. There is no explicit when-to-use or when-to-prefer-siblings guidance, despite existing padovan, padovan_step, and perrin tools that an agent could confuse with this one.

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?