Skip to main content
Glama

Markdown fence closure check

bpj_markdown_fence_coverage
Read-onlyIdempotent

Check backtick and tilde fence closure, boundaries and contained line counts.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds the scanning scope (both backtick and tilde fences, boundary handling, per-fence line counts), which is genuine behavioral context beyond the annotations, but it says nothing about how findings are reported or what triggers a failure.

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?

A single front-loaded sentence with no filler; the scope (fence types, then closure, boundaries, counts) is ordered usefully. It is a fragment rather than prose, but nothing is wasted.

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?

With no output schema, the description carries the burden of saying what comes back — pass/fail, issue list, line counts, positions — and it does not. It also omits the input size limit and any indication of how the check degrades on truncated text, leaving the agent under-informed for a tool it must call correctly.

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?

There is exactly one required parameter, "text", with 0% schema description coverage; the description never mentions it. It does not say the input is the raw markdown source, nor does it warn about the 6000-character maxLength — a real constraint an agent must plan around for large 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?

"Check backtick and tilde fence closure, boundaries and contained line counts" names a specific verb and a precise resource, and the two fence styles plus the three aspects (closure, boundaries, line counts) narrow it against siblings like bpj_markdown_fence_language_mix. It stops short of explicitly differentiating itself from those siblings, 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 statement of when to reach for this tool versus the sibling fence or markdown checks, no prerequisites, and no exclusions. The agent must infer from the title alone that this is a static markdown linting step.

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.