ScorpTech x402 Tools

Fibbinary Count

fibbinary_count

Read-onlyIdempotent

How many fibbinary numbers from 0 through n there are. Through 0 there is 1, through 2 there are 3, through 3 there are 3, through 5 there are 5, through 10 there are 8, and through 21 there are 13. n runs from 0 to 1000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/fibbinary-count

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

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 mark the tool as read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral context beyond that: pricing at $0.001 USDC per successful x402 call on Solana and an equivalent HTTPS endpoint.

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 purpose is front-loaded in the first sentence, followed by examples, bounds, and payment/endpoint details. The multiple examples add some length, but they earn their place by clarifying the sequence and inclusive counting behavior.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter counting tool with no output schema, the description covers bounds, examples, pricing, and transport. However, it never defines what a fibbinary number is, which is a meaningful domain gap for an agent that does not already know the term.

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?

The schema documents only the numeric bounds for n, with 0% description coverage. The description compensates by stating that n runs from 0 to 1000000, that the count is from 0 through n, and by giving examples such as through 0 is 1 and through 10 is 8, making the inclusive upper-bound semantics clear.

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: count how many fibbinary numbers exist from 0 through n. The examples make the operation concrete, but it does not explicitly distinguish itself from sibling tools such as fibbinary_nth, fibbinary_index, or fibbinary_next.

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?

The description explains what the tool computes and gives the valid n range, but it provides no explicit when-to-use guidance or comparison against the many related fibbinary siblings. An agent must infer that this is the counting variant rather than, for example, the nth-term tool.

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?