ScorpTech x402 Tools

Fibword

fibword

Read-onlyIdempotent

The nth bit of the infinite Fibonacci word, starting at n = 0. The word is the fixed point of 0 to 01 and 1 to 0, and it starts 01001010. n runs from 0 to 99999. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/fibword

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds important behavioral context beyond annotations: the price ($0.001 USDC per successful call via x402 on Solana) and an alternative HTTPS endpoint. This is valuable for an agent to understand cost and access methods.

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 core purpose and is generally concise, though it includes some extra detail about the Fibonacci word's definition. Every sentence contributes to understanding, but the word morphism explanation could be trimmed for brevity.

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?

Given the simplicity (one integer parameter, no output schema) and annotations covering safety, the description is largely complete. It includes pricing and an alternative endpoint, which are critical for a paid tool. A minor gap is the lack of explanation on how the x402 payment flow works, but the essential facts are present.

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?

Schema description coverage is 0%, so the description must clarify the parameter. It does so by stating 'n runs from 0 to 99999' (redundant with schema min/max) and that n is the index 'starting at n = 0'. This adds some meaning but does not fully compensate for the lack of schema descriptions.

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 verb+resource: 'The nth bit of the infinite Fibonacci word'. It precisely defines the output (a bit) and the indexing scheme, making the tool's function clear. However, it does not explicitly differentiate from the closely related sibling 'fibword_prefix', so sibling differentiation is missing.

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?

There is no guidance on when to use this tool versus alternatives. The description only defines the tool and provides pricing/endpoint info, with no mention of when-not to use it or how it compares to siblings like fibword_prefix.

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?