ScorpTech x402 API

Lucky Count

lucky_count

Read-onlyIdempotent

How many lucky numbers are from 1 through n. There is 1 through 1, 2 through 3, and 13 through 50. n runs from 1 to 100000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/lucky-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": "lucky_count"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile. The description adds useful operational context beyond annotations: pricing ($0.001 USDC per successful call), x402/Solana payment, and an HTTPS endpoint alternative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, and pricing/endpoint details are operationally relevant. However, the sentence 'There is 1 through 1, 2 through 3, and 13 through 50' is unclear and does not earn 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?

This is a simple one-parameter count tool, and the description covers bounds, cost, payment protocol, and an alternate endpoint. No output schema exists, but 'How many' sufficiently implies a count result; the only notable gap is the ambiguous example sentence.

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 description coverage is 0%, so the description must carry parameter meaning. It says n runs from 1 to 100000, which repeats the schema's min/max, and 'from 1 through n' clarifies that n is an inclusive upper bound, but it adds little else about the parameter.

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 verb and resource: 'How many lucky numbers are from 1 through n.' The count framing distinguishes it from siblings such as lucky_next and lucky_nth, though it never explicitly names those alternatives.

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?

The n range (1 to 100000) gives context for valid inputs, but there is no explicit when-to-use or when-not guidance. The count-only purpose implies usage, but the agent must infer why to choose this over lucky, lucky_nth, or lucky_next.

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?