Skip to main content
Glama

List ending consistency

bpj_parallel_list_endings
Read-onlyIdempotent

Compare terminal punctuation across bullet and numbered list items.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own: nothing about whether it parses Markdown, HTML, or plain text lists, what a 'comparison' produces, or how inconsistent items are surfaced.

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 zero filler or redundancy. Nothing in it could be cut without losing meaning.

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?

The tool is simple (one string parameter, no nesting, no output schema), so a one-line description is defensible. Still, for a comparison tool the agent is left guessing what the result looks like and what counts as a list item, which is the minimum gap that keeps this at 'adequate' rather than 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 coverage is 0% and the single parameter 'text' is titled only 'Source text' with a 6000-character cap. The description partially compensates by implying the text should contain bullet or numbered list items, but it gives no guidance on accepted list syntax, multi-list input, or how the length limit interacts with long documents.

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 uses a specific verb ('Compare') and a clearly scoped resource ('terminal punctuation across bullet and numbered list items'), which is far more informative than the tool name alone. It falls short of 5 because it does not distinguish this from nearby list-structure tools (bpj_html_list_structure, bpj_markdown_list_html) or say what the comparison yields.

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?

There is no statement of when to reach for this tool, no exclusions, and no named alternative. An agent must infer from the phrase 'bullet and numbered list items' that this is a proofreading/consistency check rather than a parser or converter.

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.