Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

gen_random

Paid $0.02 (x402, USDC Base): CSPRNG random integers [min,max] or fair pick from list. Args: min, max, n, from (comma list).

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

Input Schema

NameRequiredDescriptionDefault
nNo
maxNo
minNo
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a genuinely important trait, the $0.02 x402/USDC-Base payment requirement, which an agent could not infer elsewhere. It omits failure behavior, whether payment is charged per call or per result, and what happens when both modes' arguments are present.

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?

Two dense sentences with the cost front-loaded and the argument list trailing. Nothing is wasted, though the telegraphic style leaves some ambiguity.

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 four-parameter tool with no annotations and no output schema, the description covers the two modes and the price but not the return shape (single integer versus array), defaults, or error conditions. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, and it only names the four parameters. 'from' is clarified as a comma list, but 'n' is unexplained (count of values?), and there are no defaults, ranges, or mutual-exclusivity rules for min/max versus from.

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?

States a specific verb and resource: CSPRNG random integers in [min,max] or a fair pick from a list. That is clearly distinct from siblings like gen_uuid, gen_password, and gen_lorem, though it never names them explicitly.

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 only implied by the argument list: pass min/max for integers, or from for a list pick. There is no explicit when-to-use guidance, no statement about which mode wins if both are supplied, and no pointer to alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources