ScorpTech x402 API

Cantor Count

cantor_count

Read-onlyIdempotent

How many integers from 0 through n have only the digits 0 and 1 in base 3. The count through 0 is 1, through 2 is 2, and through 8 is 4. n runs from 0 to 999999999999999. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/cantor-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": "cantor_count"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds valuable context beyond annotations: the maximum n, example outputs, the $0.001 USDC cost per successful call, and an HTTPS endpoint alternative. It still does not describe response format or rate-limit behavior.

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?

The definition is front-loaded with the core mathematical question, followed by examples, input range, and practical access details. Every sentence adds useful information for an agent deciding whether and how to call the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only mathematical counting tool with no output schema, the description supplies the operation, input range, example outputs, cost, and alternate HTTPS endpoint. Nothing material for correct invocation appears to be missing.

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 description coverage is 0%, so the description must compensate for the single undocumented parameter. It defines n as an inclusive upper bound from 0 to 999999999999999 and provides examples at n=0, n=2, and n=8, clarifying both domain and expected output scale.

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 states a specific mathematical count: integers from 0 through n whose base-3 digits are only 0 and 1. It includes concrete example results, making the operation clear and distinguishable from sibling ternary/cantor tools, though it does not explicitly say 'returns the count' or name alternatives.

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?

The description defines the input domain but gives no guidance on when to use this tool versus alternatives such as cantor_bit or other ternary-related tools. There are no exclusions or selection criteria beyond the mathematical definition.

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?