ScorpTech x402 Tools

Primitive Abundant

primitive_abundant

Read-onlyIdempotent

Whether n is abundant and no proper divisor is abundant. 12, 18, 20, and 70 are. 24 is not, because 12 divides it. 6 is perfect, so it is 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/primitive-abundant

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

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 declare readOnly/idempotent/non-destructive, so the bar is lower, and the description adds genuinely new context: the 1–10000 domain, the $0.001 USDC per-successful-call price, and the equivalent HTTPS endpoint. It doesn't explicitly say the result is a boolean.

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?

Front-loaded with the definition, then three short worked examples (two positive, one negative, one perfect-number exclusion), then domain and cost. No filler; every sentence adds 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?

No output schema exists, so the description must convey the return value; 'Whether n is...' strongly implies a boolean but never says so explicitly. Otherwise the definition, domain, examples and payment/transport details are sufficient to call it correctly.

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 schema description coverage at 0%, the description carries the load, and it does identify n as the integer under test and restates the 1–10000 domain (already in the schema's min/max). What's missing is any hint about behavior for out-of-range input or error handling.

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 predicate: n is abundant AND no proper divisor of n is abundant. The positive examples (12, 18, 20, 70), the negative case (24, since 12 divides it) and the perfect-number exclusion (6) pin down the exact mathematical property. Against siblings like abundance, highly_abundant or superabundant this definition is unambiguous on its own terms.

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 definition rather than stated: an agent can infer it should call this for primitive-abundant classification and use abundance for a plain abundancy test, but no alternative is ever named. No prerequisites or when-not conditions are given beyond the worked examples.

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?