ScorpTech x402 API

Stern

stern

Read-onlyIdempotent

Stern's diatomic sequence. s(0) is 0, s(1) is 1, even terms repeat s(n/2), and an odd term is the sum of its two neighbors in the previous row. An optional modulus reduces the term; zero is rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/stern

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

Input Schema

Name	Required	Description	Default
`n`	Yes
`mod`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, while the description adds meaningful invocation context: x402 pricing at $0.001 USDC per successful call on Solana, an HTTPS endpoint, and rejection of zero modulus. It does not describe the response format, but for a deterministic sequence calculator the added behavioral detail is strong.

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 compact and front-loaded with the sequence definition, followed by modulus behavior, pricing, and endpoint. Every sentence contributes useful information for invoking the tool correctly.

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 simple two-parameter mathematical operation and the absence of an output schema, the description covers the sequence definition, modulus behavior, payment protocol, and endpoint adequately. It could be slightly more complete by explicitly stating that the tool returns the n-th Stern term, optionally reduced modulo mod.

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 carry semantic meaning. It explains n via the sequence recurrence and identifies mod as an optional modulus that reduces the term, but it does not clarify that mod is a decimal string up to 200 digits, nor does it explicitly state the return type; 'zero is rejected' is also somewhat ambiguous because n=0 is valid per schema.

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 names Stern's diatomic sequence specifically and gives its defining recurrence, including s(0), s(1), even-index behavior, and odd-index behavior. This uniquely distinguishes it from the many sibling sequence tools without requiring schema inspection.

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?

It explains the mathematical sequence but gives no explicit guidance on when to use this tool versus alternatives, nor any exclusions or sibling routing. Usage is only implied by the sequence name and definition.

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?