Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

gen_lorem

Paid $0.02 (x402, USDC Base): lorem ipsum generator, 1-20 randomized paragraphs. Args: p (int, default 3).

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_lorem"
  }
}

Input Schema

NameRequiredDescriptionDefault
pNo

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?

No annotations are supplied, so the description carries the full burden. It does disclose genuinely important behavior that structured fields do not: the tool is paid, costs $0.02, and settles via x402 in USDC on Base — critical context an agent needs before calling. However, it says nothing about failure or payment-decline behavior, whether output is plain lorem text versus something structured, or how the randomization works.

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

Conciseness5/5

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

A single compact line that front-loads the highest-stakes fact (the price and payment rail) before the operation and arguments. Every clause carries information and there is no filler.

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 one-parameter generator with no output schema and no annotations, the description covers price, operation, output quantity, and the argument. The only gap is return-format detail and payment-failure behavior, which is minor for a trivial generator.

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 0% and the single property "p" has no description in the schema, so the description must compensate, and it does: it renames the intent (paragraph count), states the type (int), the default (3), and the effective bounds (1-20) matching the schema minimum and maximum. A little more (e.g. what happens if p exceeds 20) would earn a 5.

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?

"Lorem ipsum generator" is a specific, concrete resource and the output shape (1-20 randomized paragraphs) is stated, which cleanly separates it from sibling generators like gen_uuid, gen_password, and gen_random. It stops short of a named sibling comparison, but the resource noun alone is distinctive enough.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the obvious alternative gen_random. The only usage-adjacent information is the paragraph count range and default, which is invocation detail rather than selection guidance.

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