Skip to main content
Glama
Sign In
mcp-server-markdown

mcp-server-markdown

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_section

Extract content from a specific heading in a markdown file until the next heading of same or higher level.

Instructions

Extract a section by heading from a markdown file. Returns content from that heading until the next heading of same or higher level.

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": {
      "file": "<file>",
      "heading": "<heading>"
    },
    "name": "get_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to the markdown file
headingYesHeading text to find (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the extraction logic (content from heading until next same/higher-level heading) and case-insensitive matching (implied from schema). However, it lacks details on error handling (e.g., if heading not found), performance, or output format beyond content extraction.

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 description is two sentences with zero waste, front-loading the core purpose and following with precise behavioral details. Every word earns its place, making it highly efficient and easy to parse.

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

Completeness4/5

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

Given the tool's moderate complexity (extraction based on heading levels) and no annotations or output schema, the description is mostly complete. It explains what the tool does and how it behaves, but lacks details on return values (e.g., structured vs. raw text) and error scenarios, leaving minor gaps.

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 100%, so the schema already documents both parameters (file path and heading text). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or edge cases. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Extract a section by heading'), resource ('from a markdown file'), and scope ('Returns content from that heading until the next heading of same or higher level'). It distinguishes itself from siblings like list_headings (which lists headings) and find_code_blocks (which finds code blocks).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (extracting content from markdown files based on headings) but doesn't explicitly state when to use this tool versus alternatives like list_headings or search_docs. No guidance is provided on prerequisites, exclusions, or specific scenarios where this tool is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools