Skip to main content
Glama

Shift Markdown heading levels

bpj_markdown_shift_heading_levels
Read-onlyIdempotent

Shift ATX heading levels outside fenced blocks and reject changes beyond levels one through six.

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>",
      "offset": "<offset>"
    },
    "name": "bpj_markdown_shift_heading_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description adds genuine behavior beyond that: fenced code blocks are skipped and resulting levels outside 1-6 cause a rejection rather than clamping. It still omits what a successful call returns (the rewritten text) and how the rejection surfaces.

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?

One front-loaded sentence with zero filler, and the exclusions (fenced blocks, out-of-range levels) are packed in efficiently. It is dense but nothing is wasted and nothing needs re-ordering.

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?

For a two-parameter pure transform, the definition covers the key edge cases but leaves the return value undefined with no output schema, and gives no hint about the input-size cap. Adequate to attempt a call, thin for predicting the result.

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 description coverage is 0%, but the schema carries meaningful titles ('Source text', 'Level offset') and bounds (-5..5, maxLength 6000). The description adds the downstream range constraint on the result but never states that a positive offset deepens and a negative one shallows headings, leaving the sign convention to inference.

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?

Specific verb (shift) plus resource (ATX heading levels), with explicit scope ('outside fenced blocks') and a stated range rule (levels one through six). An agent can tell exactly what transformation it performs; it just doesn't contrast itself with a named alternative.

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?

No when-to-use or when-not-to-use guidance, and no alternative tool named for the adjacent task (e.g. checking heading structure vs. rewriting it). The only contextual clue is the word 'Markdown', so the agent must infer applicability from the tool name 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.