Skip to main content
Glama

English hedge review

bpj_english_hedge_review
Read-onlyIdempotent

Locate common English hedging expressions an editor may want to qualify.

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_hedge_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. Beyond that the description adds nothing: it does not say whether results are returned as spans with offsets, counts, or sentences, nor whether the tool only flags or also suggests replacements.

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?

A single short sentence with no filler, and the core action is front-loaded. It is efficient, though it errs toward under-specification rather than over-verbosity.

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 one-parameter, read-only detection tool the description is close to sufficient, and annotations carry the safety profile. The notable gap is that no output schema exists, so the description should have described what a result looks like, and it does not.

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 description coverage is 0%, but there is only one parameter and its title "Source text" plus the maxLength of 6000 makes its meaning largely self-evident. The description does not compensate for the coverage gap by mentioning the input size limit or whether the text should be single-language 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 names a specific verb and resource ("Locate common English hedging expressions"), so an agent can tell this is a detection/scanning tool rather than a rewriting tool. It does not explicitly differentiate from close siblings such as bpj_english_intensifier_review or bpj_english_wordy_phrases, so the agent must infer the distinction from the phrase "hedging".

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?

The clause "an editor may want to qualify" implies an editorial review context, which hints at when to reach for it. But there is no explicit when-to-use statement, no prerequisites, and no redirection to alternative review tools for intensifiers, wordiness, or passives.

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.