Skip to main content
Glama

Readability scores

readability_scores
Read-onlyIdempotent

Calculates Flesch-Kincaid, Gunning Fog, and SMOG scores to help you judge how hard a text is to read and its grade level.

Instructions

Score how hard a text is to read with three standard formulas: Flesch Kincaid grade level (plus the Flesch reading ease score), Gunning Fog index and SMOG index. Each grade is roughly a US school grade, so 12 is the end of high school and 16 is a college degree. Input: text. SMOG is built for samples of 30 sentences or more, so on shorter text the tool still returns a number but marks it as less reliable. Example: "Give me the Flesch Kincaid, Gunning Fog and SMOG scores for this paper."

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

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault
smogYes
wordsYes
sentencesYes
syllablesYes
gunning_fogYes
complex_wordsYes
smog_reliableYes
reading_ease_labelYes
flesch_reading_easeYes
flesch_kincaid_gradeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, but the description adds real value beyond them: it explains that SMOG still returns a number on short text but flags it as unreliable, and it decodes the grade scale (12 = end of high school, 16 = college). It does not mention language constraints or how the reliability flag is surfaced, keeping it below 5.

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?

Purpose and formula list are front-loaded, then interpretation, then the input and the SMOG caveat, then an example. Every sentence carries information; the example is slightly redundant with the formula list but still clarifies phrasing.

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?

With an output schema present, the description need not explain return values, and it already covers the input, the metric meaning and the main reliability caveat. Only minor gaps remain (e.g., English-only assumption), so this is essentially complete for a one-parameter read-only tool.

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 0% for the single `text` parameter, but the description states "Input: text" and the surrounding context makes clear it is the passage to be scored. For one self-evident string parameter this is sufficient, though no format or length expectations are given beyond the SMOG note.

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?

The description uses a specific verb and resource ("score how hard a text is to read") and names the exact three formulas returned (Flesch-Kincaid, Gunning Fog, SMOG), which distinguishes it at a glance from siblings like count_text, word_frequency and style_flags.

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?

The example query ("Give me the Flesch Kincaid, Gunning Fog and SMOG scores for this paper") makes the intended trigger clear, and the SMOG sentence-sample caveat tells the agent when a result is less trustworthy. It stops short of explicitly excluding sibling tools or stating when not to use it, so it is a 4 rather than a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.