Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

slugify_text

Paid $0.02 (x402, USDC Base): Unicode-safe URL slug generator. Args: text (string), sep (default '-'), max (default 80).

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": {
      "text": "<text>"
    },
    "name": "slugify_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
sepNo
textYes

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?

With no annotations, the description does add real behavioral context: a $0.02 x402/USDC-Base payment requirement, which is essential before calling. However, it omits other behavior an agent needs, such as whether output is lowercased, how transliteration of non-ASCII characters works, or what happens on collision/empty input.

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 compact clauses, with the cost notice front-loaded before the function description and the args listed tersely at the end. Nothing is wasted, though the args list reads as a schema echo rather than added 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 3-parameter tool with no output schema and no annotations, the description covers payment and the argument surface but leaves the return value shape and the semantics of 'max' unspecified. An agent can call it, but cannot confidently predict the output format or truncation behavior.

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 0%, so the description must carry parameter meaning, and it partially does: it names all three args with types and gives defaults for sep ('-') and max (80). The critical ambiguity is what 'max' measures (characters vs words) and whether truncation adds an ellipsis, which is left unexplained.

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+resource: "Unicode-safe URL slug generator," which is unambiguous and clearly distinct from siblings like text_stats or encode_base64. It stops short of explicitly contrasting with any sibling, but the function is unique enough in the toolset that no confusion arises.

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?

The description gives no when-to-use guidance, no prerequisites beyond the payment note, and no alternatives or exclusions. An agent must infer from the name alone when slug generation is the right call.

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