ScorpTech x402 Tools

Chebyshev Rec

chebyshev_rec

Read-onlyIdempotent

One step of the Chebyshev recurrence. kind is t or u. prev is degree n-1, older is degree n-2, and value is 2xprev - older. n runs from 2 to 64. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/chebyshev-rec

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>",
      "x": "<x>"
    },
    "name": "chebyshev_rec"
  }
}

Input Schema

Name	Required	Default
`n`	Yes
`x`	Yes
`kind`	No	t

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so safety is covered. The description adds useful non-annotation context: the $0.001 USDC cost per successful call, x402/Solana payment, and an alternate HTTPS POST endpoint.

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 short, front-loads the core purpose, and avoids unnecessary prose. However, the sentence about prev/older is potentially confusing because those are not actual parameters, which slightly weakens an otherwise efficient structure.

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

Completeness3/5

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

For a simple math tool with readOnly annotations and no output schema, the description covers payment, endpoint, kind, n range, and a value formula. It remains incomplete on x's role and why prev/older are mentioned without corresponding inputs, so an agent can call it but may misunderstand exactly what is being computed.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains that kind is t or u and that n runs from 2 to 64, but it leaves x's meaning and bounds unexplained and introduces 'prev' and 'older' as if they were inputs even though they are not schema parameters.

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 states a specific resource and operation: 'One step of the Chebyshev recurrence,' with kind t/u and a value formula. It is clearly a recurrence-step math tool, but it does not explicitly distinguish itself from siblings like chebyshev_t, chebyshev_u, chebyshev_disc, or chebyshev_prod.

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 gives no explicit guidance on when to choose this tool over the related chebyshev_t, chebyshev_u, or chebyshev_prod siblings. The n range and kind enum are present, but they are constraints rather than usage guidance.

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?