Skip to main content
Glama

Wordy English phrase review

bpj_english_wordy_phrases
Read-onlyIdempotent

Find common wordy English phrases and suggest shorter equivalents.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds one piece of behavior beyond that — that output includes suggested shorter replacements, not just detections. It says nothing about how findings are returned, whether positions/spans are included, or any handling of the 6000-character limit.

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?

One front-loaded sentence with no filler; the action and its output are stated immediately. It is efficient but so terse that it omits useful detail rather than wasting words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-input text analyzer with no output schema, knowing that it detects wordy phrases and proposes shorter equivalents is close to sufficient. Still missing are the input-length ceiling, the shape of returned findings, and how it relates to the neighboring English-style review tools.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions the single "text" parameter, so it adds no meaning beyond the schema's own title "Source text" and its maxLength of 6000. With low coverage the description was expected to compensate and does not, leaving the input-size constraint undocumented in prose.

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 uses a specific verb and resource ("Find common wordy English phrases") and adds the follow-up action ("suggest shorter equivalents"), which tells an agent exactly what the tool produces. The qualifier "wordy" implicitly separates it from siblings such as hedge or intensifier reviews, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisites, and no mention of when to prefer a different review tool (e.g., hedge, intensifier, passive candidates). Usage is only inferable from the tool name and the one-sentence purpose.

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.