ScorpTech x402 API

Genocchi

genocchi

Read-onlyIdempotent

The nth Genocchi number |G(2n)|, from G(2n) = 2*(1-4^n)*B(2n) with B(1) = +1/2. The first four absolute values are 1, 1, 3, and 17. signed is (-1)^n times that value. n runs from 1 to 20. Past 15 digits a value 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/genocchi

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond that: pricing per successful call, x402/Solana payment context, an HTTPS endpoint alternative, and the fact that values over 15 digits are returned as decimal strings.

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 definition is front-loaded with the mathematical meaning and then adds practical details about range, output format, pricing, and endpoint. It is dense but not rambling; the signed note is the main piece that may not earn its place without a corresponding parameter.

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?

For a simple one-parameter math tool, the description covers the formula, examples, valid range, output representation for large values, and payment/endpoint context. It could be slightly clearer about the exact return type for smaller values and why the signed variant is mentioned.

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 compensate. It states that n runs from 1 to 20 and ties n to G(2n), but it largely repeats the schema's min/max bounds and does not fully explain the return behavior for the signed/unsigned distinction.

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 clearly identifies the resource as the nth Genocchi number |G(2n)| and includes the defining formula. It is specific and understandable, though the extra note about a signed variant is not tied to any parameter and slightly muddies what exactly is returned.

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 gives the valid n range and pricing/endpoint context, which implies when the tool can be used. However, it does not say when to use this rather than alternatives, nor does it explicitly state any exclusions or prerequisites beyond the numeric range.

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?