Skip to main content
Glama

Text level: CEFR estimate + readability (1 credit or $0.005)

check_text_level
Read-onlyIdempotent

Is this reading passage right for my learners? English text in: estimated CEFR band and audience, consensus grade, six readability formulas, vocabulary profile, long sentences, and concrete edits to reach a target level (target=A1..C2). PAID: 1 Iris Credit with a credits key (Authorization: Bearer iris_... header or the key argument; packs from $0.25, buyable with a plain USDC transfer, see payment_options), or $0.005 per call with x402 over MCP (USDC on Base) or MPP over MCP (USDC.e on Tempo). An unpaid call returns the payment terms and charges nothing; bad input is rejected first; failed work is never charged (credits are refunded). Same result as GET /v1/text/level.

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

Input Schema

NameRequiredDescriptionDefault
keyNoOptional Iris Credits key (iris_ + 48 hex). Better: set it once as the MCP header Authorization: Bearer <key>. Without a key the call is paid with x402 / MPP over MCP.
textYesEnglish text, 30+ words, max 8000 characters (POST JSON {"text": ...} also works). Omit for a demo.
targetNoOptional CEFR level you want the text to be at; the answer then includes edits to get there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent/open-world safety, while the description adds genuinely new behavioral facts: pricing and auth mechanisms, that an unpaid call returns payment terms and charges nothing, that bad input is rejected before charging, and that failed work is refunded. It also notes result parity with GET /v1/text/level.

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?

Outputs are front-loaded after a one-line framing question, and the remaining content is dense and factual. The payment paragraph is long and partly duplicates the key parameter's schema description, which keeps it from a perfect score.

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?

There is no output schema, so the description enumerates the return payload itself, and it also covers input constraints, auth paths, and billing/error behavior. Nothing an agent needs to call 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%, so key, text length limits, and the target enum are already documented. The description only restates target=A1..C2 and the alternative Authorization header, adding no new parameter semantics beyond the schema.

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 concrete outputs (estimated CEFR band, audience, consensus grade, six readability formulas, vocabulary profile, long sentences, concrete edits) for a specific resource (English text), so an agent knows exactly what comes back. It is clearly distinguishable from siblings like essay_statistics or make_study_pack.

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 opening question frames the intended use case (checking whether a passage suits learners) and the target parameter workflow is explained. It does not state when a sibling such as essay_statistics would be the better pick, so it stops short of explicit alternatives/exclusions.

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.

Resources