Burs-IA Utils

Métricas de legibilidad

readability-score

Read-onlyIdempotent

Calcula las métricas de legibilidad: LIX y RIX (independientes del idioma) y Flesch (en) o Fernández-Huerta (es) estimados. Cuándo: hay que transformar, comparar o medir un texto con exactitud y no por aproximación. No para: contar caracteres, bytes, palabras, oraciones, líneas y párrafos, y estima el tiempo de lectura (text-metrics). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Computes the language-agnostic LIX and RIX scores plus estimated Flesch Reading Ease (en) or Fernández-Huerta (es) using heuristic syllable counts; also sentence and word length averages. When: text has to be transformed, compared or measured exactly instead of approximated. Not for: counting characters (text-metrics). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`lang`	No	Language for syllable heuristics (optional; one of: en, es; default "en").	en
`text`	Yes	Text (string; required).

Output Schema

Name	Required	Description	Default
`lix`	No
`rix`	No
`words`	No
`sentences`	No
`fernandez_huerta`	No
`syllables_estimate`	No
`flesch_reading_ease`	No
`avg_letters_per_word`	No
`avg_words_per_sentence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / text / examples
```
Added value: +[
+  "The cat sat on the mat. It was happy."
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Computes the language-agnostic LIX and RIX scores plus estimated Flesch Reading Ease (en) or Fernández-Huerta (es) using heuristic syllable counts; also sentence and word length averages. When: text has to be transformed, compared or measured exactly instead of approximated. Not for: counting characters (text-metrics). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds what they don't: no network, no stored state, determinism, and concrete limits (64 KB JSON input, 1 s per call, 1 MB result). That is exactly the extra context an agent needs to avoid oversized inputs.

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 Cuándo/No para/Efectos/Límites structure is well front-loaded, but the description ships the same content twice (Spanish block plus a near-duplicate English block), which is avoidable bloat for a two-parameter tool.

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 present, return values need no explanation; the description still covers scope, language coverage, determinism, side effects and hard limits. An agent has everything needed to call it correctly.

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, but the description adds real meaning: the lang value selects Flesch (en) vs Fernández-Huerta (es) and drives heuristic syllable counting. It does not add format/size guidance for text beyond the schema's maxLength.

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?

States a specific verb (calcula) and the exact resources (LIX, RIX, Flesch/Fernández-Huerta) plus the derived averages, so an agent knows precisely what it gets. It also names the sibling it is not (text-metrics) for counting characters/words.

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?

Explicit 'Cuándo' (exact measurement/comparison of text) and 'No para' (counting characters, bytes, words, sentences, lines, paragraphs, reading time → text-metrics) with the alternative named. Nothing is left to inference.

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

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?