ScorpTech x402 Tools

Powersmooth

powersmooth

Read-onlyIdempotent

Whether n is y-power-smooth: every maximal prime-power factor p^k is at most y. 12 is 4-power-smooth and not 3-power-smooth. 8 is 8-power-smooth and not 4-power-smooth. n and y run from 1 to 1000000000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/powersmooth

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>",
      "y": "<y>"
    },
    "name": "powersmooth"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes
`y`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/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. The description adds important operational context: it is a paid x402/Solana call at $0.001 per successful call, with an alternate HTTPS endpoint. It does not detail failure or charging behavior, but with annotations the bar is lower.

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 predicate and formal definition are front-loaded, followed by clarifying examples, input ranges, price, and endpoint. The content is relevant and mostly compact, though the two examples and payment/endpoint details make it slightly longer than strictly necessary.

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?

There is no output schema, and the description does not explicitly state the return format, though 'Whether n is ...' strongly implies a boolean result. It otherwise covers inputs, mathematical semantics, cost, and endpoint for a simple two-parameter predicate.

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 description coverage is 0%, so the description must carry parameter meaning. It defines y as the bound on every maximal prime-power factor and n as the number being tested, and gives valid ranges and examples. This adds substantial semantics beyond the schema's type and min/max constraints.

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 gives a specific mathematical predicate and a formal definition: every maximal prime-power factor p^k is at most y. The worked examples clarify the meaning. It does not explicitly contrast with the sibling `smooth` tool, so sibling differentiation is not fully stated.

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?

The description states valid input ranges and operational details like price and HTTPS endpoint, but it does not say when to use this tool versus alternatives such as `smooth` or other number-theoretic predicates. Usage is only implied by the predicate itself.

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?