ScorpTech x402 Tools

Exp Divisors

exp_divisors

Read-onlyIdempotent

The exponential divisors of n, comma-separated and ascending. 8 gives 2,8. 12 gives 6,12. 16 gives 2,4,16. 36 gives 6,12,18,36. 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/exp-divisors

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

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 cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real context beyond them: the response ordering, the price ($0.001 USDC per successful call via x402 on Solana), and an alternate HTTPS endpoint. What is missing is failure behavior (e.g. what happens for out-of-range n or how payment errors surface).

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 core definition, then the examples, then constraints, then pricing/endpoint. The four examples are short and each demonstrates a different case (a prime power, 12, 16, 36), so every sentence earns its place.

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, but the description defines the return format (comma-separated, ascending), the valid input range, and the payment model, which is enough for an agent to call it correctly. Missing only edge-case behavior at the boundaries (n=1) and error/payment-failure handling.

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 parameter meaning, and it does: n is described through its domain ('1 to 1000000') and four input/output examples that make the semantics of n concrete. It does not clarify whether n must be an integer type or what 1 returns, leaving a small gap.

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?

States a specific verb+resource: 'exponential divisors of n, comma-separated and ascending', so the agent knows exactly what is computed and how it is returned. It does not name or differentiate itself from the closely related siblings exp_count, exp_sigma, or exp_next, which leaves ambiguity for an agent scanning the family.

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 only implied: the worked examples (8 -> 2,8; 36 -> 6,12,18,36) show the kind of input it accepts, and the domain restriction 'n runs from 1 to 1000000' helps. However, there is no explicit statement of when to use this tool rather than exp_sigma, exp_count, or exp_next, so the agent must infer the choice from names alone.

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?