Skip to main content
Glama
Sign In

Moltline Educator Toolkit

by com.moltlinestudio
OverviewDiscussionsAdmin

Readability Report

readability_report
Read-onlyIdempotent

Analyze teaching text with Flesch-Kincaid readability and leveling advice. FREE.

Typical input {"text": "", "target_grade": 6} returns {"flesch_kincaid_grade": 8.2, "reading_ease": 62.1, "sentences": N, "words": N, "avg_words_per_sentence": N, "long_sentences_over_25w": N, "polysyllabic_words_sample": [...], "target_grade": 6, "gap": 2.2, "suggestions": ["..."]}.

Use on teaching text where the reading level matters. Not for scores students earned (grade_curve) and not for general prose style, which the creator server's analyze_writing covers. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""} (for example {"error": "empty text"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe passage to analyze, at least one full sentence of plain text; must be non-empty.
target_gradeNoTarget grade level 1-12; when set, the report adds a gap assessment against it. 0 (default) skips it.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"The passage to analyze — at least one full sentence of plain text; must be non-empty."New value: +"The passage to analyze, at least one full sentence of plain text; must be non-empty."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so restating 'read-only and idempotent' adds little. The genuinely new content is the error contract: no protocol errors, a structured {"error": ...} payload with examples, and the guarantee that retry after correction is safe — that is behavior an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence and the usage/exclusion sentences are front-loaded and efficient, but the block of pretty-printed sample output duplicates what the output schema already provides (has_output_schema=true), and the error guidance is buried at the end after that redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and full annotations present, the description covers everything still needed: scope, alternatives, error behavior, and retry safety. Nothing an agent requires to invoke this correctly is 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?

Schema description coverage is 100%, and the schema already explains both text and target_grade, including the 0-default skip behavior. The description's example input and the 'gap' field in the sample return reinforce but do not extend the schema's semantics, so baseline 3 applies.

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 a specific verb+resource (Flesch-Kincaid readability analysis of teaching text) and enumerates the metrics produced. It explicitly distinguishes itself from grade_curve and from the creator server's analyze_writing, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

States the positive case ('Use on teaching text where the reading level matters') and two explicit exclusions with the named alternative for each (grade_curve for student scores, analyze_writing for general prose). This is the when/when-not/alternatives pattern at full strength.

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

All Moltline Educator Toolkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources