ScorpTech x402 Tools

Kynea

kynea

Read-onlyIdempotent

The nth Kynea number, (2^n + 1)^2 - 2. n=1 gives 7, n=2 gives 23, and n=3 gives 79. n runs from 1 to 128. Past 15 digits the 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/kynea

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent safety, and the description adds genuinely new behavioral facts: the valid domain 1-128, the output type switching to a decimal string past 15 digits, and the paid x402/Solana cost per successful call. It stops short of describing latency or error behavior on out-of-range n.

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?

Definition, formula, and examples are front-loaded, followed by range and output-format facts, then payment/endpoint details. Nearly every sentence earns its place; the pricing/HTTPS sentence is operationally necessary but mildly dilutes an otherwise pure-math description.

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?

With no output schema, the description usefully discloses the return type behavior (integer up to 15 digits, decimal string beyond). For a one-parameter pure function with annotations, this is close to complete; only out-of-range behavior and the returned field shape remain unspecified.

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?

Schema coverage is 0%, so the description must carry the parameter, and it does: n is defined as the exponent in the formula, illustrated with n=1/2/3 outputs, and bounded at 1-128. It adds real semantic meaning beyond the bare integer type, though it does not say what happens if n falls outside the range.

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?

Names the specific mathematical object (Kynea number) and gives its closed form '(2^n + 1)^2 - 2' plus concrete sample values (7, 23, 79). This unambiguously separates it from numeric siblings like carol or cullen without the agent needing to guess.

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?

The domain is narrow enough that the intended use is implied by the formula and domain (n=1..128), but the description never states when to pick this over the many adjacent sequence tools, nor any exclusion criteria. Usage is inferable rather than guided.

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?