Skip to main content
Glama

Automated Readability Index

bpj_automated_readability_index
Read-onlyIdempotent

Estimate US grade level from English alphanumeric characters, words and sentences using ARI.

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

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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered structurally. The description adds that the computation is derived from characters, words and sentences on English alphanumeric input, which is useful behavioral context, but it says nothing about the response shape or precision.

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 front-loaded sentence with no filler, naming the metric, the target unit and the method. It is efficient but so terse that useful detail is omitted rather than wasted.

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 simple one-parameter calculator this covers the essentials, and there is no output schema, so the description would ideally state that a numeric grade-level score is returned and roughly how to interpret it. The language restriction is implied but the length limit and output form are missing.

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 required parameter and 0% schema description coverage, the description does carry some weight: it implies the input should be English prose whose character/word/sentence counts are meaningful. However it never mentions the 6000-character cap or what happens with non-alphanumeric or non-English content, leaving the main constraint undocumented in prose.

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 a specific verb ('Estimate'), a specific output ('US grade level'), and the underlying method ('ARI') applied to English alphanumeric text. It does not explicitly distinguish itself from the sibling readability tool (bpj_lix_readability_index), so an agent must infer that ARI vs Lix are different formulas.

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?

No when-to-use or when-not-to-use guidance, and no mention of the sibling readability index as an alternative. The only implicit constraint is that the text must be English, which functions as an input precondition rather than tool selection 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.