Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

x402node_math_random

Generate cryptographically secure random integers or floats within a specified range. Get up to 100 numbers in a single call.

Instructions

Random number generator / random integer / random float / dice roll / lottery numbers / coin flip / cryptographically secure random / RNG / number picker. Generate cryptographically secure random numbers in a range with optional batch count.

Price: unknown on Base (auto-paid in USDC).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402node_math_random"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many (default 1, max 100)
maxNoMaximum (default 100)
minNoMinimum (default 0)
typeNoint | float (default int)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Description mentions 'cryptographically secure' and optional batch count, but lacks details on side effects, idempotence, error handling, or cost implications (price note is not behavioral). No annotations are present to compensate.

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 description is somewhat verbose with an extensive list of aliases before the core sentence. While functional, it could be more concise without losing meaning.

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

Completeness3/5

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

For a simple tool with well-documented parameters, the description provides adequate context. However, it does not describe the output format (e.g., single number vs. array), and includes irrelevant price information.

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 100% with descriptions for all parameters (count, min, max, type). The description adds no extra semantic depth beyond what the schema already provides, achieving baseline.

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 the tool generates cryptographically secure random numbers in a range with optional batch count. The aliases list covers diverse use cases like dice roll or coin flip, but it does not differentiate from related siblings like x402node_crypto_random-bytes or cn402_iching_random.

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?

No explicit guidance on when to use this tool versus alternatives. The aliases imply general random number tasks, but no comparative context or exclusions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools