Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Word count and readability: count words, characters and sentences and estimate reading time and readability

text_stats
Read-only

Count characters, words, sentences and paragraphs, estimate reading and speaking time, and compute the Flesch reading-ease score and grade level for English text. Use to check the length and readability of a draft. Example: text=The quick brown fox jumps over the lazy dog. It was not amused.. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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
textYesThe text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=false; the description goes further by disclosing the cost model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free) and by tying the non-idempotency to billing ("each call is charged, so repeats are not free"). The English-only limitation is also real behavioral context beyond the annotations.

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?

Front-loaded with the enumeration of outputs, then usage, then the example, then billing — a sensible order. The final billing/pricing sentence is dense with several clauses and could be trimmed, but nothing is redundant 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?

No output schema exists, but the description enumerates the computed metrics (counts, times, Flesch ease, grade level), which effectively tells the agent what comes back. Combined with the language limitation and pricing, an agent has enough to call it correctly; only the exact response shape is left implicit.

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 and the schema covers it, so the baseline is already high. The description adds a worked example ("text=The quick brown fox...") that shows what the input looks like in practice, giving slight meaning beyond the thin schema description "The text".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verbs and resources: counts characters, words, sentences and paragraphs, estimates reading/speaking time, and computes Flesch reading-ease and grade level. This clearly separates it from nearby siblings like text_keyword_density or number_words, which measure different things.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use to check the length and readability of a draft" gives a concrete usage context, and "for English text" implicitly excludes non-English inputs (e.g. text_language territory). It stops short of naming an explicit alternative or when-not-to-use condition, so it is clear but not complete routing 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.