Skip to main content
Glama

Extract a Markdown section

bpj_markdown_cut_section
Read-onlyIdempotent

Extract the first matching ATX heading and its content through the next same-or-higher level heading.

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>",
      "title": "<title>"
    },
    "name": "bpj_markdown_cut_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
titleYes

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 readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description earns credit for disclosing real scope semantics — it returns only the first match and stops at the next same-or-higher heading — but it says nothing about what happens when no heading matches, whether matching is case-sensitive, or whether heading-like lines inside code fences are honored.

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 boundary rule is stated immediately after the action. It is efficient, though the extreme brevity leaves obvious gaps unaddressed.

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 small two-parameter pure function with annotations covering the safety profile, the core contract is conveyed. However, with no output schema the description should say what a successful extraction returns and what a non-match looks like, and it omits both.

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%, so the description must carry the burden; it adds only the notion of title matching ('first matching') and implies text is a Markdown document. It does not clarify exactness/case sensitivity of the title match or that text is capped at 6000 characters for a reason.

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 (extract) and a specific resource (an ATX heading section), and pins down the boundary condition ('through the next same-or-higher level heading'), which an agent can act on directly. It does not differentiate from the sibling bpj_markdown_section_index, so it falls short of 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 when-to-use guidance at all: nothing says to call bpj_markdown_section_index first to discover the exact title, or when a whole-document read is preferable. The only usage signal is implicit in the word 'matching'.

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.