Skip to main content
Glama

Repeated question and exclamation marks

bpj_punctuation_runs
Read-onlyIdempotent

Locate consecutive question or exclamation marks for tone 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_punctuation_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

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 openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the purpose framing ('tone review') and says nothing about matching rules — whether mixed sequences like '?!' count, whether two marks is the threshold, or what the result looks like.

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 short sentence, front-loaded with the action and resource, with no wasted clauses. The trailing 'for tone review' is the only element that could be seen as decorative, but it does supply usage framing.

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 text scan with no output schema and one trivial parameter, the definition is adequate but thin: it never clarifies what 'consecutive' means (two or more? which mark combinations?) nor what 'locate' yields (offsets, snippets, counts). An agent can call it, but cannot predict its results precisely.

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?

There is a single required parameter, 'text', whose schema entry gives only a title and a 6000-character cap with 0% description coverage. The description never mentions the input at all, so it adds no meaning beyond the schema — though for a one-parameter text input the schema is largely self-explanatory, keeping this at the minimum-viable level.

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 pairs a specific verb ('Locate') with a specific resource ('consecutive question or exclamation marks'), so the agent knows exactly what is being found. It does not explicitly distinguish itself from the sibling bpj_punctuation_inventory, leaving the boundary between counting all punctuation and finding repeated-mark runs implicit.

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?

The phrase 'for tone review' implies the context in which to reach for this tool, but there is no explicit when-to-use/when-not guidance and no named alternative for the closely related inventory tool. Usage is inferred rather than stated.

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.