ScorpTech x402 Tools

Padovan Step

padovan_step

Read-onlyIdempotent

The Padovan step identity P(n) = P(n-1) + P(n-5). left is P(n-1) and right is P(n-5). n runs from 5 to 8192. Past 15 digits a term 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/padovan-step

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

Input Schema

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

Adds real context beyond annotations: pricing ($0.001 USDC per successful call via x402 on Solana), an alternative HTTPS endpoint, and a return-format rule (terms past 15 digits come back as decimal strings). Annotations already cover read-only/idempotent, so this paid-call and serialization info is genuinely additive. It doesn't mention failure/refund behavior for failed calls.

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?

Four short sentences, front-loaded with the mathematical definition before the operational details (range, formatting, price, endpoint). Every sentence carries information, though the endpoint URL is arguably container metadata.

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?

With no output schema, the description carries the burden of return semantics and does reasonably: it names the two outputs and the >15-digit string rule. Missing is the exact response shape (field names, types, whether left/right are keys) and any error behavior, which would help a calling agent.

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?

The schema has 0% description coverage, so the description must compensate; it gives n's domain (5 to 8192) and the P(n) notation establishes n as a term index, but the bounds merely repeat the schema's min/max and no further semantics are added. Baseline 3.

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?

States the specific recurrence identity P(n) = P(n-1) + P(n-5) and defines the two returned components (left = P(n-1), right = P(n-5)), which pins down what a 'step' tool does. It doesn't explicitly distinguish itself from siblings padovan or padovan_sum, but the step semantics are clear from the formula.

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 only implied by the name and formula; there is no statement of when to pick this over padovan (full term), padovan_sum, or the analogous *_step siblings. An agent can infer it, but nothing routes it explicitly.

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?