Skip to main content
Glama

Sentence length profile

bpj_sentence_length_profile
Read-onlyIdempotent

Segment English sentences, then calculate individual word counts and the mean sentence length.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation, so the description does not need to restate safety. It adds the useful fact that processing is a two-stage pipeline (segment, then count), but it is silent on how English segmentation handles abbreviations, decimals, or non-English input, and on whether the mean is over sentences or words.

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 tight sentence with the two operations in execution order and nothing superfluous. Structure is good, though front-loading the input expectation ('English text') would have helped more than the sequencing word 'then'.

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 analysis tool with no output schema, the description covers the input domain and the computed fields at a high level. It stops short of describing the result shape (per-sentence records plus an aggregate mean) that an agent would need to consume the output without guesswork.

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 0% and the single parameter carries only a maxLength of 6000, so the description is the only place the 'English text' expectation is stated. It does not explain what happens past the length limit or whether HTML/markup should be stripped, leaving the main semantic constraint implicit.

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?

States two concrete operations: segmentation of English sentences and computation of per-sentence word counts plus mean length. That is specific enough to distinguish it from siblings like bpj_long_sentence_shortlist or bpj_sentence_ending_moods, though the description never explicitly contrasts with them and only the name/title hints at the 'profile' shape of the result.

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 guidance on when to use this versus the many other sentence-related siblings, no prerequisites, and no exclusions. An agent must infer from the name alone that this is for aggregate length statistics rather than shortlisting long sentences.

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.