ScorpTech x402 Tools

Tetranacci Index

tetranacci_index

Read-onlyIdempotent

The smallest index n with T(n) equal to value. 0 is index 0, and 1 is index 3. A number that is not a Tetranacci term, or a leading zero, is rejected. value is a decimal integer of at most 600 digits. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/tetranacci-index

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": {
      "value": "<value>"
    },
    "name": "tetranacci_index"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, and the description adds meaningful context beyond that: rejection rules, a 600-digit limit, payment cost, and an HTTPS endpoint. There is no contradiction with the annotations.

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?

The description is front-loaded with the core definition, then adds constraints and payment/endpoint details. Every sentence contributes practical information for invocation.

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

Completeness5/5

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

For a one-parameter, idempotent lookup tool without an output schema, the description covers purpose, input validity, the returned concept, and payment/endpoint context. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% property description coverage, so the description must carry the burden. It defines value as a decimal integer of at most 600 digits, states that leading zeros and non-Tetranacci terms are rejected, and clarifies the special index mappings for 0 and 1.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific inverse operation: the smallest index n where T(n) equals value, and explicitly defines the indexing convention for 0 and 1. This clearly distinguishes it from term-generating siblings such as tetranacci or tetranacci_sum.

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?

It explains invalid-input conditions (non-Tetranacci terms and leading zeros) and the input size limit, which is useful usage context. However, it does not explicitly say when to use this tool versus sibling alternatives like tetranacci, leaving the choice implied by the inverse-lookup purpose.

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?