ScorpTech x402 API

Range Lcm

range_lcm

Read-onlyIdempotent

The least common multiple of the integers from lo through hi. The LCM of 1 through 10 is 2520, and the LCM of 1 through 11 is 27720. lo must not pass hi. Each end runs from 1 to 40. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/range-lcm

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": {
      "lo": "<lo>",
      "hi": "<hi>"
    },
    "name": "range_lcm"
  }
}

Input Schema

Name	Required	Description	Default
`hi`	Yes
`lo`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond annotations: pricing ($0.001 USDC per successful x402 call), an HTTPS endpoint, and the constraint that lo must not pass hi. It does not mention error behavior when lo > hi, which would be helpful.

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 and the examples are useful for confirming inclusive range behavior. The pricing and endpoint sentences add relevant invocation context but are slightly tangential to the core mathematical definition.

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 two-parameter pure computation with no output schema, the description covers the core operation, domain, relationship constraint, examples, cost, and alternate endpoint. It could be slightly more complete by explicitly stating that the return value is an integer or describing error behavior for invalid ranges.

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 carry parameter meaning. It does well by explaining that lo and hi are inclusive range ends, that lo must not exceed hi, and that each end runs from 1 to 40; examples further clarify inclusive semantics. Minor gap: it does not individually label lo and hi beyond their role in the phrase.

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?

The description states a specific mathematical operation and scope: 'The least common multiple of the integers from lo through hi.' It clearly distinguishes the tool from sibling arithmetic utilities by naming the exact computation and range.

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 clear mathematical purpose, but the description does not explicitly say when to use this versus alternatives or when not to use it. No sibling tool is named for comparison.

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?