Skip to main content
Glama

English intensifier review

bpj_english_intensifier_review
Read-onlyIdempotent

Locate common English intensifiers and return their positions for review.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds a useful behavioral fact — it reports positions rather than rewriting text — but says nothing about what counts as an intensifier, whether matches are case-sensitive, or how position is expressed (offset vs. line/column).

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 tightly written sentence with the action and result front-loaded; nothing is padded. The trailing "for review" is slightly redundant, but there is no structural or length problem.

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 analyzer with full annotations, the description covers the essentials, but the absence of an output schema makes the vague "positions" claim the only clue about the return shape. It is minimally adequate, not complete.

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%, so only the field name "text" and title "Source text" convey meaning, and the description adds nothing about it. With a single self-evident input (the text to scan) the omission is mild, but the description could have clarified whether HTML/markup or non-English content is acceptable given the 6000-character cap.

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?

"Locate common English intensifiers and return their positions" gives a concrete verb plus a clearly bounded linguistic resource, and the return (positions) is stated. It is distinguishable from the sibling hedge/passive/pronoun reviewers by naming the specific category, though it never explicitly contrasts itself with them.

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 guidance on when to use this versus the adjacent English-style reviewers (hedges, wordy phrases, passives), nor any prerequisite such as input language or plain-text expectations. The agent must infer the use case (editing/style review) from the name alone.

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.