Skip to main content
Glama

Analyze the tone, formality and reading level of a text

text_tone
Read-only

Tone analysis of a text (max 10,000 characters): formality 0-1, sentiment, emotion scores, tone labels such as friendly, aggressive or urgent, and short suggestions. The reading level (Flesch-Kincaid grade) is computed in code with a simple syllable count, so treat it as an estimate. Model judgements are not measurements. Related tools on this server, for a different need: text_paraphrase when you need to generate a rewrite of a text in another tone; text_answer when you need answers a question from the given text only. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to analyse (max 10,000 characters)

Output Schema

NameRequiredDescriptionDefault
noteNo
tonesNo
emotionsNo
checkedAtNo
formalityNo
sentimentNo
suggestionsNo
readingLevelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / checkedAt
      Added value: +{}
    • addedOutput schema / properties / emotions
      Added value: +{}
    • addedOutput schema / properties / formality
      Added value: +{}
    • addedOutput schema / properties / note
      Added value: +{}
    • addedOutput schema / properties / readingLevel
      Added value: +{}
    • addedOutput schema / properties / sentiment
      Added value: +{}
    • addedOutput schema / properties / suggestions
      Added value: +{}
    • addedOutput schema / properties / tones
      Added value: +{}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description still adds material context: a 10,000-character input ceiling, the pricing model ($0.002 per successful call via x402 with failed calls uncharged), and a reliability caveat that the Flesch-Kincaid grade uses a simple syllable count and that 'model judgements are not measurements.' The pricing and failure-charging details are exactly the kind of 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.

Conciseness4/5

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

The description is front-loaded: what it returns, then the reliability caveat, then alternatives, then price. Every element is useful, but the payment sentence carries some incidental weight ('USDC on Base, Solana and 10 more networks') that is not needed to invoke the tool correctly.

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?

An output schema exists, so return values need no explanation, and the description covers everything else that matters for a one-parameter analysis tool: input ceiling, output field meanings, accuracy caveat, sibling routing, and cost. Nothing an agent needs in order to call it 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?

There is only one parameter and schema description coverage is 100%, so the schema already documents 'text' and its 10,000-character limit. The description restates the same limit without adding format, encoding, or language expectations, so the baseline of 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?

The first sentence names a specific verb and resource ('Tone analysis of a text') and enumerates exactly what the tool returns: formality 0-1, sentiment, emotion scores, tone labels, and suggestions. It also distinguishes itself from text_paraphrase and text_answer by function, so an agent can separate this from its siblings 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 Guidelines4/5

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

The description explicitly routes the agent away from this tool for two adjacent needs: 'text_paraphrase when you need to generate a rewrite' and 'text_answer when you need answers a question from the given text only.' That is clear conditional guidance, though it only frames the alternatives and never states a positive exclusion such as 'do not use for sentiment-only scoring' or what this tool should not be used for.

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