Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

English readability metrics

seo-content_readability-score
Read-onlyIdempotent

Compute Flesch Reading Ease, Flesch-Kincaid, Gunning Fog, SMOG and Coleman-Liau from caller text. Price $0.02 USDC. POST /api/v1/seo-content/readability-score. An unpaid call returns the x402 payment terms and does not run.

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": "seo-content_readability-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYestext, string, length 1 to 200000. Required.
languageNolanguage, string. Required.en

Output Schema

NameRequiredDescriptionDefault
smogNosmog. Number.
countsNocounts. Object.
sourcesNosources. Array.
gunningFogNogunningFog. Number.
colemanLiauNocolemanLiau. Number.
limitationsNolimitations. Array.
smogReliableNosmogReliable. Boolean.
avgSentenceLengthNoavgSentenceLength. Number.
fleschReadingEaseNofleschReadingEase. Number.
fleschKincaidGradeNofleschKincaidGrade. Number.
avgSyllablesPerWordNoavgSyllablesPerWord. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is inherited. The description adds genuinely non-inferable behavior: a $0.02 USDC charge, the concrete endpoint path, and the failure mode where an unpaid call returns payment terms without executing. It stops short of stating rate limits or what the paid response contains, but the payment gate is the critical operational detail and it is disclosed.

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

Conciseness5/5

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

Three tight sentences: what is computed, what it costs, where it lives, and how failure behaves. Front-loaded with the metric list and free of filler, with the payment caveat placed last where it belongs as a precondition.

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?

An output schema exists, so return values need no prose, and the description supplies the pricing and endpoint context the schema cannot. The only real gap is the language parameter: the title says English metrics, but nothing explains whether a non-'en' value changes or breaks the computation.

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 the two parameters are already documented and the baseline of 3 applies. The phrase 'from caller text' corroborates the text parameter but adds no format, encoding, or size guidance beyond the schema's maxLength of 200000, and the language parameter is never mentioned in the description despite the English-only framing of the title.

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

Purpose4/5

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

Names a specific verb (compute) and enumerates the exact metrics returned (Flesch Reading Ease, Flesch-Kincaid, Gunning Fog, SMOG, Coleman-Liau) against a named input (caller text). It does not explicitly distinguish itself from siblings like seo-content_topic-coverage-score, but the enumerated metric list makes its scope unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the metric names rather than stated: there is no 'use this when you need X instead of Y' guidance and no mention of alternatives among the scoring siblings. The one genuine usage rule given is a precondition — an unpaid call returns x402 payment terms and does not run — which is useful but operational rather than selective.

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