ScorpTech x402 API

Smith

smith

Read-onlyIdempotent

Whether n is a composite Smith number: its digit sum equals the digit sum of its prime factors with multiplicity. 4, 22, 27, and 121 are. 6 and every prime are not. n runs from 1 to 1000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/smith

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

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, open-world; the description adds genuinely new behavior: a per-call price of $0.001 USDC charged only on success, the x402/Solana payment protocol, and an equivalent HTTPS endpoint. That payment and cost detail is real value the annotations do not carry.

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, then examples, range, and cost/endpoint. Nearly every clause earns its place; the negative examples are the most valuable part. Slightly dense as a single run-on block rather than separated statements.

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 boolean predicate with no output schema, the description is sufficient: the definition, example outcomes, and input domain give an agent everything needed to call it correctly. The implicit boolean return is clear from 'Whether n is...', though stating the return type explicitly would close the last 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%, so the description must speak for the lone parameter, and it only says 'n runs from 1 to 1000000' — a restatement of the schema's min/max. It does signal that n is the candidate integer being tested, but adds no format or edge-case semantics beyond that.

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 predicate with the exact mathematical definition: whether n is a composite Smith number, digit sum equals digit sum of prime factors with multiplicity. It also enumerates positive and negative examples (4, 22, 27, 121 yes; 6 and every prime no), which pins the concept down unambiguously against sibling number-theory predicates.

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 rather than guided: supply an integer in 1..1,000,000 and get a yes/no. No mention of when to prefer this over related siblings (hoax, smarandache, equidigital) or of edge cases beyond 'every prime is not'. The HTTPS/endpoint alternative is an access-path note, not tool-selection 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 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?