Skip to main content
Glama

Word Counter API - words, characters, sentences, reading time, top words

word_counter
Read-onlyIdempotent

Count words, characters, sentences and paragraphs, reading and speaking time, average word length and the most used words. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/word-counter.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "Hello world, this is a short sample text."
    },
    "name": "word_counter"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text

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?

Beyond the readOnly/idempotent/openWorld annotations, the description discloses server-side execution, immediate deletion of data with nothing stored, and a concrete rate limit plus paid tier with payment endpoint. Minor friction: it mentions 'files are deleted' while the schema accepts only a text string, which is slightly misleading about what is actually transmitted.

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?

Three short sentences, front-loaded with what gets counted before trust and pricing details. Every sentence carries information; the x402 URL is slightly dense but is genuinely useful for an agent that must pay.

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 counting utility with annotations and no output schema, the description covers capabilities, privacy, and cost. The remaining gap is that the exact return shape (field names, per-metric structure) is only implied by the enumeration rather than stated, which matters since no output schema exists.

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?

There is a single required parameter whose schema description coverage is 100% ('The text'), so the schema already carries parameter meaning. The description does not add constraints such as size limits, language handling, or encoding behavior, so it stays at the baseline for high schema coverage.

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 gives a concrete verb ('Count') and enumerates the exact metrics produced: words, characters, sentences, paragraphs, reading/speaking time, average word length, and top words. This makes the tool unmistakable without opening the schema, though it does not explicitly contrast with any sibling utility.

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 named alternative. The quota/pricing sentences imply a precondition (25 free calls/day, then paid via x402) but never state conditions for selecting this tool over another approach such as local counting.

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