Skip to main content
Glama

English passive candidates

bpj_english_passive_candidates
Read-onlyIdempotent

Flag forms of be followed by common participles as candidates for editorial 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_passive_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral signal: results are 'candidates', i.e. heuristic flags requiring human judgement, not definitive findings. It says nothing about what a match looks like (offsets, counts, excerpts) or whether only 'common' participles from a fixed list are matched.

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?

A single fifteen-word sentence with the action and the detection rule front-loaded and no filler. Nothing in it is redundant or restates the tool name verbatim.

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 heuristic checker with annotations covering safety and no output schema, the description is close to sufficient but leaves two gaps an agent needs: the semantics of the input text and the shape of the returned flags. It is adequate rather than complete.

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%, so the single 'text' parameter relies entirely on its title and maxLength of 6000 for meaning. The description never mentions the input at all — not that it takes the source text, not whether it accepts a document or a fragment, and not how the 6000-character limit should be handled. The reference to 'English' only weakly implies English-language input.

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 gives a concrete detection rule (forms of 'be' followed by common participles) and a concrete action (flag as candidates for editorial review), which is far more specific than the name alone. It stops short of positioning itself against the sibling review tools (hedge, intensifier, wordy phrases), so an agent must infer the distinction from the linguistic pattern named.

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 implied by 'candidates for editorial review', which signals the output is advisory and meant to be triaged rather than acted on directly. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling review tools, and no note about expected false positives from the heuristic.

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.