ScorpTech x402 Tools

Euler Zigzag Sum

euler_zigzag_sum

Read-onlyIdempotent

The sum of Euler zigzag numbers a(0) through a(n). The sum through a(5) is 26, and the sum through a(10) is 60201. n runs from 0 to 40. 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/euler-zigzag-sum

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/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), yet the description still adds real context: the domain limit n<=40, the precision switch where results beyond 15 digits come back as decimal strings, and a pay-per-call cost of $0.001 USDC with an HTTPS fallback endpoint. Auth/payment requirements and output-type transitions are exactly the kind of detail annotations cannot express.

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?

Five short sentences, front-loaded with the definition and examples before the operational details (range, precision, price, endpoint). Nothing is redundant; even the pricing line earns its place for an x402 paid tool.

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 correctly takes on return-value semantics by explaining the number-vs-decimal-string threshold, and it covers cost and transport. Only error/out-of-range behavior is unaddressed, a minor gap for a one-parameter deterministic math tool.

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 load, and it does: it names n, states the 0..40 domain (matching schema min/max), and gives two sample values that let an agent sanity-check its input and expected result. It does not spell out what happens for out-of-range n, keeping it short of a 5.

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?

States a precise verb+resource: the cumulative sum of Euler zigzag numbers a(0) through a(n), which implicitly distinguishes it from the sibling euler_zigzag (single term). The two worked examples (n=5 -> 26, n=10 -> 60201) pin down exactly what 'sum' means so there is no ambiguity about inclusive bounds.

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?

Usage is implied by the math definition and the stated valid range n = 0..40, but there is no explicit 'use euler_zigzag if you only need the nth term' routing or any note on when this is preferable to the sibling. For a pure-function tool with an obvious single purpose that is adequate, not exemplary.

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?