Skip to main content
Glama

readability_grade

Read-onlyIdempotent

Deterministic Flesch Reading Ease and Flesch-Kincaid Grade Level for a block of text, plus word/sentence/syllable counts and a plain-language reading-ease band (very_easy through very_confusing). Syllable counting is the standard vowel-group heuristic (same approximation used by textstat and most open readability tools), not a dictionary lookup. Optionally pass target_grade to get an on_target flag (within +/-2.0 grade levels). Different metric family from humanizer_score - this is pure readability statistics, not AI-writing-tell detection. Deterministic, no LLM.

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

Input Schema

NameRequiredDescriptionDefault
textYesProse to analyze. Max 100,000 characters.
target_gradeNoOptional target Flesch-Kincaid grade level, 0-20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, closed-world); the description adds substantial behavior beyond that: determinism with no LLM calls, the vowel-group syllable heuristic and its known approximation limits versus a dictionary lookup, and the fact that target_grade yields an on_target flag at a +/-2.0 grade tolerance. These are exactly the caveats an agent needs to trust and interpret the numbers.

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?

Front-loaded with the metric names, then caveats, then sibling disambiguation - good ordering with no filler. The only waste is the repeated determinism claim ('Deterministic Flesch...' opening and 'Deterministic, no LLM.' closing), which says the same thing twice.

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?

No output schema exists, and the description compensates by enumerating the return fields: the two scores, three counts, a named band scale (very_easy through very_confusing), and the optional on_target flag. For a 2-parameter pure function this is close to fully specified; only the precise return shape/keys are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by explaining what target_grade actually changes behaviorally - it produces an on_target flag using a +/-2.0 grade-level tolerance - which is nowhere in the schema's 'Optional target Flesch-Kincaid grade level, 0-20.' The text parameter only inherits its limit from the schema, so no extra credit there.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact metrics produced (Flesch Reading Ease, Flesch-Kincaid Grade Level) plus the ancillary outputs (word/sentence/syllable counts, reading-ease band), and explicitly distinguishes itself from the sibling humanizer_score. An agent can tell from the first sentence what this returns and that it is a statistics tool, not a detection tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear routing rule against the closest sibling: 'Different metric family from humanizer_score - this is pure readability statistics, not AI-writing-tell detection.' That resolves the main selection ambiguity in the sibling list. It stops short of stating explicit when-not conditions (e.g. don't use for non-prose input, or for text above the 100k limit) beyond what the schema covers.

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.