Skip to main content
Glama

Text length and byte counts

bpj_text_inspect
Read-onlyIdempotent

Count Unicode code points, UTF-8 bytes, lines and whitespace-delimited fields to check size limits.

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": "bpj_text_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive behavior, so safety is covered. The description adds the measurement semantics (which quantities are counted), which is genuine value. It stops short of saying whether counts are computed on the raw string or after trimming, and there is no output schema to describe the returned shape.

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?

A single sentence that front-loads the verbs and enumerates the measured quantities without filler. Efficient and easy to scan. It is dense enough that a little structure (e.g. separating what is counted from what it is for) could improve readability.

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, read-only inspection tool with clear annotations, the description covers purpose and the quantities measured. It is incomplete in that no output schema exists and the description does not indicate what the result contains (per-metric values? totals?), nor how it relates to the sibling counting/estimation tools.

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%, but there is only one parameter, 'text', whose name and type make its meaning self-evident, and maxLength 12000 is documented in the schema. The description frames what is measured but adds no constraint or format detail about the input beyond the obvious. Adequate but with no compensating depth.

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 specific operations on a specific resource: counting Unicode code points, UTF-8 bytes, lines and whitespace-delimited fields, with the stated aim of checking size limits. That is far more concrete than a tautology. It does not differentiate itself from nearby tools such as bpj_reading_length_estimate or bpj_chunk_text, which keeps it from a 5.

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?

The phrase 'to check size limits' implies the use case, giving a context for invocation. However, it never states when to prefer this over the sibling length/estimate tools, and offers no exclusions or prerequisites. Usage is implied rather than directed.

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.