Skip to main content
Glama

Coleman–Liau grade estimate

bpj_coleman_liau_grade
Read-onlyIdempotent

Estimate English reading grade from letters and sentences per hundred words.

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

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine context beyond them: the result is an estimate, it applies to English only, and it is computed from letters and words-per-sentence counts. It does not say what happens with very short or non-English input, which matters for a statistical estimator.

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?

A single front-loaded sentence with no filler; the metric definition is packed into the purpose clause rather than padded out.

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?

For a one-parameter, annotation-rich, no-output-schema tool this is close to sufficient — purpose, language scope, and computation basis are all stated. A brief note on minimum input length or the scale of the returned grade would close the remaining 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?

With one parameter at 0% schema description coverage, the description must carry the load. Saying 'letters and sentences per hundred words' implicitly tells the caller to pass full running prose (not a word list) and that it must be English, which is real value; however it never addresses the 6000-character limit or short-text behavior handled only by the schema.

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 states a specific verb and resource ('Estimate English reading grade') and, via 'letters and sentences per hundred words', pins down the exact Coleman–Liau formulation rather than readability in general. That distinguishes it from siblings like bpj_automated_readability_index or bpj_reading_length_estimate, though it never names an alternative explicitly.

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 when-to-use guidance, no prerequisites, and no routing among the many readability/estimate siblings. The agent must infer that this applies to English prose grading from the purpose statement alone.

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.