Skip to main content
Glama

text-stats

Send plain text as the raw POST body and get back word count, sentence count, character count, estimated reading minutes, and the top 10 keywords (stopwords removed). Free: 3 calls a day per visitor; after that $0.01 per call via x402 at https://tools.orchardshop.xyz/t/text-stats.

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

Input Schema

NameRequiredDescriptionDefault
bodyYesPOST / with plain text as the body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does well on cost and input format: 3 free calls per visitor per day, then $0.01 per call via x402, plus the requirement that text be the raw POST body. It says nothing about error handling, size limits on input, how keywords are ranked, or behavior when stopword filtering leaves fewer than 10 terms.

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?

Two sentences, both earning their place: the first front-loads what the tool does and returns, the second front-loads the pricing constraint. No filler, no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description fully enumerates the returned metrics, and it also covers input format and cost model. For a single-parameter, stateless utility that is everything an agent needs in order to decide to call it and to call it correctly.

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?

Only one parameter exists and schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by clarifying that the text is the raw POST body (no JSON wrapper) and must be plain text, which the schema's terse 'POST / with plain text' implies but does not spell out.

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 action (send plain text in the raw POST body) and exhaustively enumerates the result set: word count, sentence count, character count, reading minutes, top 10 keywords. It is clearly a text-analysis tool rather than a converter like page-to-text or markdown-strip, though it never explicitly routes the agent away from siblings.

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 implied by the input contract (plain text must be supplied directly as the body), and the pricing/free-tier note gives practical context for calling it. However there is no explicit when-to-use or when-not guidance, and no named alternative for cases where the text lives on a web page (e.g., a sibling that fetches pages).

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