ScorpTech x402 API

Automorphic

automorphic

Read-onlyIdempotent

Whether n^2 ends with n. 1, 5, 6, 25, 76, 376, 625, and 9376 do. 10 does not. n runs from 1 to 10000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/automorphic

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

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 the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-structured context: the domain restriction n ∈ [1, 10000], a per-call price of $0.001 USDC via x402 on Solana, and an HTTPS fallback endpoint. It stops short of stating the return shape (presumably boolean), which matters since there is no output schema.

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?

Three short sentences, front-loaded with the predicate and its examples, then the domain, then the payment/transport note. Nothing is padded and every clause carries operational information.

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 single-integer predicate tool with no output schema, the definition covers semantics, domain, cost, and a transport alternative; only the return value (boolean true/false vs. a descriptive object) is left implicit. That is a small but real gap.

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; it defines n as the integer whose square is compared to its own suffix and repeats the 1–10000 range that the schema only encodes as numeric bounds. That leaves no ambiguity about what to pass, though the range is redundant with the schema's min/max.

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 mathematical predicate (n^2 ends with n, i.e. automorphic numbers) and immediately grounds it with worked examples ('1, 5, 6, 25, 76, 376, 625, and 9376 do. 10 does not.'). Against siblings like trimorphic or narcissistic, an agent can tell exactly which property is being tested without opening the 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?

There is no explicit statement of when to call this versus a sibling (e.g. trimorphic, narcissistic), nor any exclusions. Usage is strongly implied by the worked positive/negative examples, which is enough to infer intent, but the description does not do the routing work.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScorpTech x402 API 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?