ScorpTech x402 Tools

Seventh Sum

seventh_sum

Read-onlyIdempotent

The sum of the first n seventh powers, n^2(n+1)^2(3n^4+6n^3-n^2-4n+2)/24. The sum through 10 is 18080425. n runs from 0 to 10000. 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/seventh-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": "seventh_sum"
  }
}

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 declare read-only, idempotent, non-destructive, and open-world behavior, so the description adds useful context beyond them: the valid n range, example output, decimal-string formatting past 15 digits, and per-call pricing. It does not contradict the annotations and covers the main behavioral details an agent needs.

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 front-loaded with the purpose and formula, followed by range, output formatting, pricing, and endpoint details. The formula is long but directly relevant, and there is little wasted text.

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 mathematical tool with annotations and no output schema, the description is largely complete: it explains the operation, domain, example, output formatting, and payment context. Minor ambiguity remains around exact return typing below the 15-digit threshold.

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?

With one required parameter and 0% schema description coverage, the description compensates by defining n as the number of seventh-power terms, giving its range, and showing an example result. The schema still carries type and bounds, but the description adds meaningful semantic context.

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 states a specific mathematical operation: the sum of the first n seventh powers, with the closed-form formula and an example. It is naturally distinguishable from sibling sum tools such as fourth_sum, fifth_sum, and sixth_sum by naming seventh powers explicitly.

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 precise mathematical definition and the tool name, but the description does not explicitly say when to choose this over related tools or discuss alternatives. It does provide practical access context through pricing and an HTTPS endpoint.

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?