ScorpTech x402 API

Polydivisible Count

polydivisible_count

Read-onlyIdempotent

How many polydivisible numbers from 0 through n there are. Through 1 there are 2, through 10 there are 11, through 12 there are 12, and through 30 there are 21. n runs from 0 to 100000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/polydivisible-count

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds useful context beyond annotations: cost ($0.001 USDC per successful call), x402/Solana payment behavior, and an alternative HTTPS endpoint.

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?

The definition is front-loaded, followed by examples, range, pricing, and an alternative endpoint. The four worked examples are somewhat redundant but useful for a counting tool; overall the description is appropriately sized and has little wasted text.

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 simple one-parameter mathematical counting tool with no output schema, the description adequately explains the return value through examples and states the input range. It is missing a formal definition of a polydivisible number, but the sibling tool name and common mathematical meaning fill that 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 compensate. It does state that n runs from 0 to 100000 and gives example outputs through 1, 10, 12, and 30, clarifying that n is an inclusive upper bound and what the returned count looks like. However, it does not define 'polydivisible' or provide deeper semantics for n beyond the range already present in the schema.

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?

The description clearly states that this tool counts polydivisible numbers from 0 through n, which distinguishes it from the sibling polydivisible tool that likely operates on individual numbers or lists them. The phrasing is somewhat awkward, but the verb-equivalent ('how many') and resource ('polydivisible numbers') are clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus the sibling polydivisible tool or other counting tools. The examples and range provide context, but the description never states alternatives, exclusions, or decision conditions.

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?