ScorpTech x402 API

Zeckendorf Sum

zeckendorf_sum

Read-onlyIdempotent

Sum Fibonacci numbers by index, using F1 = 1 and F2 = 1. Indices must be at least 2 and no two may be consecutive. Indices 11, 6, and 4 sum to 100. An empty list is rejected. At most 64 indices, each at most 512. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/zeckendorf-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": {
      "indices": "<indices>"
    },
    "name": "zeckendorf_sum"
  }
}

Input Schema

Name	Required	Description	Default
`indices`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses cost ($0.001 USDC per successful call via x402 on Solana) and an alternate HTTPS endpoint, plus validation-failure behavior. That is meaningful operational context the annotations cannot convey; only the return shape is left unstated.

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 definition and constraint, then evidence via example, then limits, then pricing and transport. Every sentence (including the 11/6/4→100 example and the x402 note) carries information the agent needs; nothing is filler.

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 single-parameter, read-only computation with no output schema, the definition covers input rules, edge cases, cost, and alternate transport, which is enough to call it correctly. It stops short of saying what the result is (a single integer sum), the one remaining gap.

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 carries the full burden and does it well: it defines the indices parameter's meaning (Fibonacci indices with F1=1, F2=1), a minimum of 2, the non-consecutive rule, and the 64-item / 512-value caps, plus a concrete example. Minor tension with the schema's stated minimum of 0, but the description is the more precise source.

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 a specific verb and resource ('Sum Fibonacci numbers by index, using F1 = 1 and F2 = 1') and embeds the Zeckendorf non-consecutive constraint, which separates it from plain Fibonacci-style siblings. It never names a sibling such as zeckendorf or zeckendorf_bits, so differentiation is implicit rather than explicit.

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?

The description gives hard usage constraints (indices must be at least 2, no two consecutive, empty list rejected, max 64 entries, each at most 512) plus a worked example, which tells the agent when a call is legal. It offers no guidance on when to choose this over the many related Fibonacci/Zeckendorf siblings.

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?