Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

text_stats

Paid $0.02 (x402, USDC Base): text analytics - chars, words, sentences, paragraphs, reading time, top keywords. Args: text (string).

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description still discloses a genuinely important operational fact: the call is paid, costing $0.02 via x402 on USDC Base. That is behavior an agent cannot learn from the schema and prevents surprise charges. It does not cover limits on input size, empty-text behavior, or error modes, keeping it below a 5.

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?

A single compact sentence with zero padding, front-loading the payment requirement before capability and arguments. Structure is functional, though the terse 'Args:' fragment is slightly telegraphic.

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, read-only analytics tool with no output schema, the description is largely sufficient: it lists the metrics returned and flags the cost of the call. Only edge-case behavior (very long input, non-text payloads) is unaddressed, which is a minor gap at this complexity level.

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 would need to carry the meaning of the single parameter, but 'Args: text (string)' merely restates the schema type and name. No format, size constraint, or encoding guidance is added.

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 names a concrete resource and enumerates the computed metrics: 'chars, words, sentences, paragraphs, reading time, top keywords'. That is enough for an agent to distinguish it from transformation siblings like slugify_text or read_url_text, though it does not explicitly name a contrasting sibling.

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 list of returned metrics; there is no explicit statement of when to call it, when not to, or what alternative to use for related text tasks. An agent can infer the use case but must do the inference itself.

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