Skip to main content
Glama

Preferred terminology audit

bpj_editorial_term_preference
Read-onlyIdempotent

Find case-sensitive literal uses of deprecated terminology using supplied old|preferred pairs.

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>",
      "terms": "<terms>"
    },
    "name": "bpj_editorial_term_preference"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
termsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 closed-world, so the safety profile is covered. The description adds genuinely useful behavioral semantics absent from the annotations — matching is literal and case-sensitive, and terms arrive as old|preferred pairs. It does not disclose the result shape (counts vs. match locations), which is the main remaining gap.

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 the verb first and zero filler — nothing to trim. Brevity here is close to the floor of what a two-parameter tool can be described with, though it trades some detail away.

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?

With no output schema, the description is the only place a caller could learn what comes back — match spans, counts, or a pass/fail verdict — and it says nothing. For a simple read-only text audit the core information (what is searched, what patterns are supplied, how matching works) is present, so it is adequate but 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 the description carries real weight, and it does explain that 'terms' is a set of old|preferred pairs and that 'text' is the corpus searched. However, it adds nothing about the line-per-pair delimiter rules, escaping, blank lines, or the maxLength limits (6000/1500), so the schema still leaves the caller guessing on formatting.

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?

States a specific verb ('Find') and a precisely scoped resource ('case-sensitive literal uses of deprecated terminology'), plus the mechanism ('supplied old|preferred pairs'). An agent immediately knows this is a terminology audit rather than a rewrite, spell-check, or regex tool. No sibling is named as an alternative, but the sibling list contains no obvious competing terminology tool.

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?

There is no explicit when-to-use/when-not-to-use statement, but 'case-sensitive literal' implicitly bounds the tool's applicability: it will not catch case variants, inflections, or fuzzy matches. That is implied scope guidance rather than stated guidance, so it lands at minimum-viable rather than strong.

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.