Skip to main content
Glama

Markdown base anchor collisions

bpj_markdown_heading_collisions
Read-onlyIdempotent

Find heading titles that generate the same base anchor before numeric suffixes.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyLong, idempotent, non-destructive, closed-world behavior, and the description does not contradict them. It adds one genuinely useful behavioral detail: collisions are counted on the base anchor prior to numeric de-duplication, which defines what gets reported. It says nothing about output shape, ordering, or how repeated titles are grouped.

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; the disambiguating clause ('before numeric suffixes') follows the main claim and every word earns its place.

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 and annotations carry the safety profile, but with no output schema the description should say what a result looks like (list of colliding titles, groups, or counts) and what input it expects. Those gaps keep it at minimum-viable completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description never mentions the sole parameter; it only implies markdown-like input via 'heading titles'. The required flag, the 6000-character maxLength, and the expected input format are undocumented outside the schema's bare title 'Source text'.

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 gives a specific verb ('Find') and resource ('heading titles that generate the same base anchor'), and the 'before numeric suffixes' clause pins down exactly what kind of collision is meant. It does not name a sibling (e.g. bpj_markdown_internal_fragments or bpj_heading_outline_check) to distinguish itself, so a 4 rather than a 5.

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 guidance on when to use this tool, no prerequisites, and no mention of an alternative for related anchor/fragment checks. The agent must infer the use case from the purpose sentence alone.

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.