Skip to main content
Glama

Text statistics

bursia_text_stats
Read-onlyIdempotent

Count characters, words, lines and estimate tokens (~4 chars/token) of a text. Pure computation, 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": "bursia_text_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to measure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / text / description
      Added value: +"The text to measure."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds two pieces of context the annotations don't carry: it is pure local computation and free (no cost/quota exposure), and tokens are an approximation at ~4 chars/token, which prevents the agent from treating the count as exact. No return shape/pagination note, but not applicable.

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 short sentences, zero filler; the metric enumeration is front-loaded and the cost/approximation caveat follows immediately.

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?

With no output schema, the description usefully enumerates the returned metrics (characters, words, lines, token estimate), which is the key completeness need here. It does not describe the response structure beyond the field list or edge cases such as empty text, a minor gap.

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 100% and the single parameter is documented as "The text to measure," so the schema does the work. The description adds nothing about the parameter itself, which is the expected baseline-3 case for a fully documented single param.

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 a specific verb (count) with an enumerated set of resources (characters, words, lines, estimated tokens) plus the token ratio used. This is clearly distinguishable from siblings like levenshtein or url_parse, 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 Guidelines3/5

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

"Pure computation, free" gives useful context for choosing it over cost-incurring or network tools, and usage is implied strongly by the metric list. However, it names no alternatives and gives no explicit when-not 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.

Resources