Skip to main content
Glama

Voice consistency

brand_voice_consistency
Read-only

Check brand voice consistency across samples. Give samples (a list, or text with samples separated by a line of ---, or by blank lines; 2 to 40) and optionally rules (plain lines or JSON: banned words, 'use X not Y', capitalisation of names, punctuation bans, max sentence length, required terms) and bannedWords. Returns per-sample sentence length (mean, spread, longest), contractions, you/we use, a 0 to 100 formality score from transparent measures, drift flags where a sample is 15+ formality points or 35% in sentence length from the set, rule violations by sample, and required terms that never appear. Heuristic, English only; it compares samples with each other, not with a standard.

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": {
      "samples": "<samples>"
    },
    "name": "brand_voice_consistency"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesNoVoice rules: lines of text, or a JSON object/array
samplesYesThe pieces of copy to compare (2 to 40)
bannedWordsNoExtra banned words or phrases

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses substantive behavior: it returns per-sample sentence length metrics, contraction and pronoun use, a 0-100 formality score, drift flags at specific thresholds, rule violations, and missing required terms. It also states the heuristic and English-only scope, giving an agent a clear picture of what the tool does and does not do.

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?

The description is front-loaded with the core purpose, then efficiently covers inputs, outputs, and limitations. Despite being dense, every clause carries useful information and there is no filler.

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 carries the burden of explaining return values, and it does so thoroughly: sentence metrics, formality score, drift flags, rule violations, and missing required terms. It also supplies input constraints and limitations, making the definition complete for correct invocation.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds meaningful detail beyond the schema: it explains accepted samples formats, the 2 to 40 range, and describes rules contents such as banned words, 'use X not Y', capitalisation, punctuation bans, max sentence length, and required terms. This substantially improves correct parameter construction.

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?

The description states a specific verb and resource: 'Check brand voice consistency across samples.' It also clarifies the comparative nature ('compares samples with each other, not with a standard'), but it does not explicitly distinguish this tool from nearby siblings such as lint_brand_voice or plain_language_check.

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?

It gives clear input context: samples may be a list or text separated by '---' or blank lines, with a 2 to 40 limit, and rules may be provided optionally. It also states key limitations ('Heuristic, English only') and the comparative rather than standard-based approach, but it does not name when to use an alternative sibling tool instead.

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