Skip to main content
Glama

Tagline review

tagline_review
Read-only

Review taglines. Give taglines (1 to 25, one per line), optionally brand (to flag repeating the name) and cliches (extra phrases to flag). Checks word and character count, about 90 stock phrases and fillers, abstract words, three-item lists, 'where X meets Y' constructions, exclamation marks, and concreteness (numbers or named things). Returns a 0 to 100 concreteness score per line, issues, and a flag when the line could be used by any competitor. A heuristic aid; it does not check uniqueness or legal status.

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": {
      "taglines": "<taglines>"
    },
    "name": "tagline_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand name
clichesNoExtra phrases to flag
taglinesYesTaglines, one per line (1 to 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive behavior, and the description adds real value on top: it discloses the heuristic nature, the scoring model (0-100 concreteness per line), the competitor-reusability flag, and the explicit limits (no uniqueness/legal check). Return shape is described but not itemized structurally.

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?

Parameter guidance comes first, then what is checked, then what is returned, then the caveat — front-loaded and deliberately ordered. No filler sentences; every clause adds information.

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 no output schema available, the description fully carries the return-value burden (per-line concreteness score, issues, competitor flag) and states the tool's epistemic limits. An agent has everything needed to decide to call it and interpret the result.

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 all three params are documented, and the description still adds purpose-level meaning: brand is used 'to flag repeating the name', cliches are 'extra phrases to flag', and taglines are '1 to 25, one per line'. The only minor gap is that the string-vs-array acceptance isn't restated.

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 (review) and resource (taglines), then enumerates exactly what is checked — length, ~90 stock phrases, abstract words, three-item lists, 'where X meets Y', exclamations, concreteness. This distinguishes it cleanly from near-neighbours like review_microcopy, review_ui_copy, and lint_brand_voice, which target different copy types.

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?

Gives an explicit exclusion ('does not check uniqueness or legal status') and explains the conditional use of brand and cliches, so an agent knows the boundaries. It stops short of naming an alternative tool to use for those excluded checks, so no full 5.

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