ScorpTech x402 Tools

Cubefull

cubefull

Read-onlyIdempotent

Whether n is cubefull: 1, or every prime factor's exponent is at least 3. 1 and 8 are cubefull. 36 is powerful but not cubefull. n runs 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/cubefull

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new operational context: a per-call price ($0.001 USDC via x402 on Solana) and an alternate HTTPS endpoint. This cost and transport information is material for an agent orchestrating a paid API and is not captured by structured fields.

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?

Front-loaded with the definition and examples before logistics; each sentence earns its place. Slightly multi-purpose (math plus pricing/endpoint), but no filler.

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 one-parameter predicate with annotations covering safety and no output schema, the definition plus the 'whether' phrasing implicitly conveys a boolean result and gives payment/transport details. Only a fully explicit return-value statement is missing, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single param, but the description's 'n runs from 1 to 1000000000000' merely restates the schema's min/max rather than adding syntax or constraints. The definition implies n is the integer to test, but there is no extra semantic detail beyond what the schema already encodes.

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 specific verb-plus-predicate ('whether n is cubefull') and gives the exact mathematical definition, so an agent knows precisely what is being tested. It even differentiates the adjacent concept explicitly ('36 is powerful but not cubefull'), distinguishing it from the powerful sibling without opening a schema.

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?

Provides useful framing (input range 1..1e12, a clarifying example) but never states when to use it versus alternatives or any prerequisites, which are only implied by the definition. Adequate for a trivial predicate but no explicit when/when-not 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?