Skip to main content
Glama

Markdown thematic break index

bpj_markdown_horizontal_dividers
Read-onlyIdempotent

List candidate thematic break lines of three or more matching asterisks, underscores or hyphens.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds value by defining the detection rule and hedging with 'candidate', which tells the agent results are heuristic matches rather than confirmed rendered breaks. It does not disclose whether fenced/indented code is excluded or what the return shape is.

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?

One sentence, front-loaded with the verb and the qualifying rule, with zero redundant wording.

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 should say what a 'list of candidate lines' contains (line numbers, raw text, offsets) and whether code blocks are considered. It is adequate to identify the tool but leaves the agent guessing about the response shape for a tool whose whole value is the returned index.

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 one parameter with 0% schema description coverage, so the description must carry the load; it implies the input is markdown source to scan but adds nothing about the 6000-character limit or input expectations. Low stakes given a single self-evident string parameter, but no real meaning is added beyond the schema's 'Source text' title.

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 ('List') and a precisely defined resource ('candidate thematic break lines'), and even spells out the structural rule (three or more matching asterisks, underscores or hyphens). An agent can distinguish this from siblings like bpj_markdown_hard_break_positions, though no sibling is named explicitly.

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 narrow, single-purpose framing implies when the tool applies, but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as hard-break or fence tools. The word 'candidate' faintly signals a heuristic scan but is not explained.

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.