ScorpTech x402 API

Tetranacci Step

tetranacci_step

Read-onlyIdempotent

The Tetranacci step T(n) = T(n-1) + T(n-2) + T(n-3) + T(n-4). a is T(n-4), b is T(n-3), c is T(n-2), and d is T(n-1). n runs from 4 to 4096. 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/tetranacci-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": "tetranacci_step"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive). The description adds the valid range of n (4–4096), the output format (decimal string past 15 digits), pricing details ($0.001 USDC per call via x402 on Solana), and an HTTPS alternative endpoint. It does not explain seed behavior or error handling, which limits it to a 4.

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 formula and then lists constraints, output format, and pricing. It is efficient and avoids unnecessary repitition, though pricing and endpoint details could be considered secondary for core function understanding.

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

Completeness2/5

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

Given a mathematical tool with only n as input and no output schema, the description omits critical information: the initial seed values required to compute T(n), and a clear statement of the return value (e.g., 'returns T(n) as an integer, or decimal string past 15 digits'). Without seeds, the computation is underspecified.

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

Parameters2/5

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

The single parameter n has 0% schema description coverage, and the description only repeats the min/max range already in the schema. It does not clarify how a,b,c,d are determined from n, leaving the agent unable to predict the result for a given n.

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

Purpose3/5

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

The description provides the Tetranacci recurrence formula and defines a,b,c,d in terms of n, making it clear this is a mathematical step function. However, it never states that the tool computes T(n) from a single index n, nor does it specify the initial seed values. With so many sibling tools (tetranacci, tetranacci_sum, tetranacci_index, etc.), the exact purpose remains ambiguous.

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?

No guidance is given on when to use this tool versus alternatives like tetranacci, tetranacci_sum, or tetranacci_index. The description also doesn't mention prerequisites or exclusions.

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?