Skip to main content
Glama
MCP Toolkit

MCP Toolkit

text_analyze

Count words, characters, and lines in text to measure content length and structure.

Instructions

Count words, characters, and lines in text.

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_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not say the operation is a pure, side-effect-free read with no network or state mutation. More importantly, it leaves the operative definitions undefined: whether "words" means whitespace-delimited tokens, how "lines" handles a trailing or missing newline, and whether "characters" means Unicode code points, grapheme clusters, or bytes.

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?

One short sentence, front-loaded with the verb and the measured quantities, with no filler or redundancy. It is efficient, though the extreme brevity is partly a symptom of the missing semantics noted elsewhere.

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

Completeness3/5

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

For a one-parameter utility this is close to adequate, but with no annotations and no output schema the agent gets no information about the response shape (result key names, numeric types) or edge-case behavior on empty or very large input. A short clause on return format and counting rules would close the 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 description coverage is 0%, so the description must compensate; it only implies the single parameter is the text to measure and adds no constraint such as size limits, required encoding, or rejection of empty input. With just one string parameter that is required and named "text", the gap is small but real.

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 specific verb ("Count") and enumerates the exact metrics produced (words, characters, lines) over a named resource (text), so an agent knows precisely what the tool returns conceptually. It does not need sibling differentiation because none of the listed siblings (base64_convert, json_format, sha256_hash, etc.) overlap with text metrics.

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 statement of when to use this versus alternatives, no prerequisites, and no exclusions or limits (e.g., input size, encoding assumptions). The single sentence provides purpose only; an agent must infer applicability entirely from the verb.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.