Skip to main content
Glama

Unexpanded initialisms

bpj_unexpanded_initialisms
Read-onlyIdempotent

List uppercase initialisms without a parenthesized introduction for manual 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_unexpanded_initialisms"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description adds the meaningful behavioral detail that results are meant for manual review (detection, not correction), but says nothing about ordering, match granularity, or whether matches inside code/URLs are excluded. That is an acceptable but not rich addition given annotation coverage.

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 front-loaded sentence with no filler; every word (uppercase, initialisms, parenthesized introduction, manual review) carries information.

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 read-only, single-parameter analyzer with no output schema, the definition covers the input concept and the review-oriented intent. It does not describe what a returned item looks like (the string itself, its position, context), which matters for a tool whose name promises a list.

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?

One parameter with 0% schema description coverage; the description implies the single input is the text to scan but never states it explicitly, nor mentions constraints such as the schema's maxLength of 6000. The meaning is easily inferred from context, so it is adequate rather than deficient.

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?

"List uppercase initialisms without a parenthesized introduction" names a specific verb (List) and a precise resource (initialisms lacking a parenthesized expansion), and the detection criterion is unambiguous. It doesn't reference any sibling, but the sibling list is a large grab bag of unrelated analyzers, so differentiation is less critical here.

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?

"For manual review" implies the intended use (this tool flags candidates; a human decides), which is useful implied guidance. However, there is no explicit when-to-use/when-not, no statement of prerequisites, and no alternative named for cases where automatic fixing or a different check is wanted.

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.