Skip to main content
Glama

Style flags

style_flags
Read-onlyIdempotent

Flag passive voice, repeated sentence openings, filler words, and overly long sentences in essay drafts to prompt targeted revision.

Instructions

Flag common style problems in an essay: sentences in the passive voice, sentences that start with the same word as a neighbour (or three or more times), filler words and phrases such as very, just, in order to, and sentences that are too long. Inputs: text, and optional max_sentence_words (default 30), the length above which a sentence counts as long. Sentence numbers start at 1 and follow the order of the text, so number 3 is the third sentence. The sentence_list field gives each passive or long sentence with its number, and the text summary ends with a line listing those numbers. The checks are simple pattern rules, so treat them as prompts to reread, not as errors. Example: "Flag passive voice and filler words in my draft."

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

Input Schema

NameRequiredDescriptionDefault
textYes
max_sentence_wordsNoSentence length that counts as long. Default 30.

Output Schema

NameRequiredDescriptionDefault
fillerYes
sentencesYes
filler_countYes
passive_countYes
sentence_listYes
long_sentencesYes
repeated_openersYes
passive_sentencesYes
max_sentence_wordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the lower bar applies, and the description adds real signal on top: the checks are 'simple pattern rules' and should be treated as reread prompts rather than errors – an important expectation-setter about false positives. It also discloses that results are keyed to 1-based sentence numbers and echoed in a summary line, though it doesn't mention any result limits or cost for long essays.

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?

Front-loaded with the purpose, then Inputs, then output shape, then a caveat, then an example – a sensible order. A few sentences are redundant (long-sentence detection is described twice, and the sentence-numbering rule is stated in two consecutive sentences), but nothing is wasteful enough to harm comprehension.

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?

For a 2-parameter read-only analyzer with an output schema, the description covers purpose, the two parameters, sentence numbering, and the pattern-rule caveat. It spends words explaining return fields the output schema already covers, while omitting practical matters like how much text is practical to submit.

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 coverage is 50%: max_sentence_words is documented in the schema, and the description only restates it ('default 30, the length above which a sentence counts as long') without adding constraints like the 5–200 range. The required `text` parameter gets no elaboration beyond the fact that it is an essay. Adequate, but no value beyond the structured fields.

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?

Specific verb+resource: 'Flag common style problems in an essay', with the checks enumerated (passive voice, repeated sentence openers, filler words, overlong sentences). An agent can tell this apart from count_text or readability_scores, though the description never names the closest sibling, sentence_variety, which plausibly overlaps on the long-sentence check.

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 only implied through the closing example ("Flag passive voice and filler words in my draft") and the note that results are 'prompts to reread, not errors'. There is no explicit when-to-use, no when-not-to-use, and no routing to check_word_limit, sentence_variety, or readability_scores.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.