Skip to main content
Glama

Agent Exchange store

util_random

$0.001 via x402: Cryptographically random integers between min and max (default 1 to 100), or floats with float=true; n up to 100. Pay 0.001 USDC through https://store.agentexchange.work/gw/util/random?min=1&max=6&n=2 Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
nNon
maxNomax
minNomin
floatNofloat
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the cost model ($0.001 via x402, USDC, Coinbase settlement) and gateway, which is genuinely useful behavioral context. It omits rate limits, retry/refund behavior, and what a response looks like, leaving meaningful gaps for a paid mutation-like call.

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 core semantics are front-loaded and useful, but the price is stated twice ('$0.001 via x402' and 'Pay 0.001 USDC') and a full example URL with query string is embedded inline, which bloats an otherwise short 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 5-parameter, no-output-schema, no-annotation tool, the description covers the payment model, parameter defaults, and bounds adequately. It lacks return-format and error/payment-failure behavior, but the essential calling information is present.

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 coverage is nominally 100%, but the schema descriptions are trivial single-word repeats ('n', 'max', 'min', 'float'), so the description does real work: it defines the default range (1 to 100), the float=true flag for floats, and the n upper bound (100). It adds meaning beyond the schema, though x_payment is only clarified in the schema itself.

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 operation (cryptographically random integers between min and max, or floats) with concrete defaults and range, which is clearly distinct from siblings like util_uuid, util_hash, and util_time. It does not explicitly name a sibling to differentiate against, but the resource is unambiguous.

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 through the payment instructions and the example URL; there is no explicit statement of when to choose this over util_uuid or other randomness-like siblings, nor prerequisites beyond paying. The payment path ('Pay 0.001 USDC through...') does give actionable invocation context.

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