Skip to main content
Glama

Mixed English spelling pairs

bpj_mixed_english_spellings
Read-onlyIdempotent

Check for pairs of common British and American spellings used in the same document.

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

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 readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds one real behavioral detail — detection requires both variants to appear within the same document rather than flagging a single spelling — but says nothing about which word list is used, case sensitivity, or what is reported back.

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 front-loaded sentence with no filler. It is efficient, though the brevity is what leaves the guidance gaps noted elsewhere.

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 checker with no output schema, the description is barely sufficient: it names the task but omits the return shape, the capitalization/word-list behavior, and the input length limit the schema enforces.

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?

Only one parameter and schema description coverage is 0%, so the description carries the burden of explaining the input. 'Same document' loosely maps to the 'text' parameter, but nothing in the description mentions the 6000-character cap, whether plain text vs markup is expected, or how the text should be supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and object ('Check for pairs of common British and American spellings') plus the scope constraint ('used in the same document'), which cleanly separates it from siblings like bpj_english_wordy_phrases or bpj_english_hedge_review that target different editorial issues.

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?

No indication of when to prefer this over the other English-review tools, no prerequisites, and no exclusions. The phrase 'used in the same document' hints at the scenario (mixed-variant inconsistency) but the agent must infer that itself.

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.