Skip to main content
Glama

LIX readability index

bpj_lix_readability_index
Read-onlyIdempotent

Add words per sentence and the percentage of words longer than six letters to calculate LIX.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description's only added behavioral content is the computation method itself, which tells the agent how the score is derived but says nothing about the return value, the scale of the LIX score, or how text over the 6000-character cap is handled.

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 short sentence with no filler, and the operative verb ('calculate LIX') lands at the end of an unambiguous clause. Efficient, though the ordering puts the mechanics ahead of the purpose.

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?

With one required parameter, no output schema, and full annotation coverage, the definition needs only to confirm the input is source text and indicate what comes back. It omits both the input framing and any indication of the return value or score interpretation, leaving a noticeable but not fatal gap for a simple single-parameter read-only tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden of explaining the single 'text' parameter and does not do so — it never states that the input is the text to be scored, nor does it mention the maxLength of 6000 or what happens beyond it. The formula terms ('words per sentence', 'words longer than six letters') hint at the kind of content expected but add no real parameter meaning.

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

Purpose3/5

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

The description identifies the operation as computing a LIX readability index and even names the formula components (words per sentence, percentage of words longer than six letters). However, it is framed as a formula recipe rather than a statement of what the tool takes and produces, and it never mentions that the input is a block of source text to be analyzed. The sibling bpj_automated_readability_index is not distinguished from it in any way.

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?

There is no when-to-use guidance, no statement of when another readability measure such as bpj_automated_readability_index would be preferable, and no prerequisites or input constraints. The agent is left to infer everything about selection from the name alone.

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.