Skip to main content
Glama

Brand voice

lint_brand_voice
Read-only

Check text against brand voice rules. Give text and rules (a string of plain lines, or a JSON object, or an array). Understood rules: banned words or phrases, preferred terms ('use sign in not log in', or 'log in -> sign in'), required capitalisation of product names, sentence case or title case for headings (markdown # lines or heading: prefixes), a maximum sentence length in words, banned punctuation (exclamation marks, em-dashes, ellipses, emoji, ampersands, all caps), required terms, and tone words to avoid ('tone to avoid: salesy'). Rules are parsed forgivingly and echoed back so a misread rule can be corrected. Returns violations with line number, offending text, the rule and a suggested replacement, plus the rules that never matched anything.

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>",
      "rules": "<rules>"
    },
    "name": "lint_brand_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe copy to check. Use # lines or 'heading:' prefixes to mark headings.
rulesYesVoice rules: plain lines (one rule per line) or a JSON object such as {"banned": [...], "preferred": {"log in": "sign in"}, "products": [...], "headings": "sentence", "maxSentenceWords": 20, "punctuation": ["!"], "required": [...], "tone": [...]}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description still adds substantial behavioral detail: forgiving rule parsing, echoing rules back for correction, and reporting rules that never matched anything. With no output schema present, it fully carries the burden of describing the response shape (line number, offending text, rule, suggested replacement).

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?

Purpose is front-loaded in the first sentence, and the long middle sentence earns its length by enumerating concrete rule types the agent can pass. It is dense rather than padded, though a bulleted rule list would be easier to scan than one long comma chain.

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?

For a two-parameter, read-only lint tool with a 100%-covered schema and no output schema, nothing material is missing: input shapes, heading marking convention, rule grammar, forgiving parsing, and the violation report contents are all stated.

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 parameters are already documented, but the description goes further by showing the accepted rule grammars ('use sign in not log in', 'log in -> sign in', 'tone to avoid: salesy') and the free-form string/JSON-object/array flexibility of the rules input. That is genuine meaning beyond the schema's oneOf declaration.

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?

Opens with a specific verb+resource ('Check text against brand voice rules') and enumerates the rule categories it understands, which makes its scope unmistakable. It never names or contrasts with nearby siblings such as review_ui_copy or lint_disclosure_copy, so an agent must infer the boundary itself.

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?

It describes how to call it ('Give text and rules...') and notes that rules are parsed forgivingly and echoed back so a misread rule can be corrected, which implies an iterate-then-fix workflow. But there is no explicit when-to-use / when-not guidance and no routing away from the sibling copy linting tools.

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