Skip to main content
Glama

Markdown local fragment links

bpj_markdown_internal_fragments
Read-onlyIdempotent

Compare inline fragment links against local anchors generated from ATX headings.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds the important scope that comparisons are against anchors generated specifically from ATX headings, but it does not describe the output format, report shape, or any limitations such as duplicate anchors or case sensitivity.

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?

The definition is a single, front-loaded sentence with no redundant or filler wording. Every word contributes to the stated comparison.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool whose core behavior is a comparison, the definition omits what the comparison produces—whether it returns broken links, counts, a pass/fail result, or detailed mismatches. With no output schema and no parameter explanation, the description leaves significant gaps for correct invocation and interpretation.

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?

The single parameter 'text' has no schema description (0% coverage), and the description never states that this parameter is the Markdown source to be analyzed. The agent can infer this from the tool name and parameter title, but the description itself adds no explicit meaning about format, length, or content expectations.

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 ('Compare') and clearly identifies both operands: inline fragment links and local anchors generated from ATX headings. This is enough for a technical agent to understand the tool's function, though it does not explicitly distinguish it from related siblings like bpj_html_fragment_targets or bpj_markdown_heading_collisions.

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 explicit guidance on when to use this tool, when not to use it, or which sibling tool to prefer for adjacent tasks. The usage is only implied by the comparison of Markdown fragment links, leaving the agent to infer the intended context.

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.