Tools MCP Server

Overview Schema Source Related Servers Discussions Admin

markdown_insert_toc

Replace /toc markers in markdown with a generated table of contents based on document headings, automatically creating a clickable TOC.

Instructions

Replace /toc markers in markdown with generated table of contents. Finds lines containing only '/toc' and replaces them with a TOC based on document 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": {
      "markdown": "<markdown>"
    },
    "name": "markdown_insert_toc"
  }
}

Input Schema

Name	Required	Description
`markdown`	Yes	The markdown content with /toc markers to replace.
`maxLevel`	No	Maximum heading level to include (1-6). Defaults to 6.
`minLevel`	No	Minimum heading level to include (1-6). Defaults to auto-detect from document.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states the core behavior (replaces exact '/toc' lines with a TOC) but does not mention return value, side effects, or handling of edge cases like missing headings or multiple markers.

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, front-loaded with the action, and contains no filler. Every word contributes to understanding the tool's purpose.

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?

For a simple tool, the description is reasonably complete: it explains the core mechanism (replacing markers with heading-based TOC) and the schema covers parameters. It lacks explicit differentiation from sibling tools, but the focus on '/toc' markers provides sufficient context.

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 coverage is 100%, so the schema fully documents all three parameters. The description adds no additional meaning beyond what the schema already provides, earning the baseline score.

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 uses a specific verb ('Replace') with a clear resource ('/toc markers in markdown') and outcome ('generated table of contents based on headings'). It distinguishes from sibling tools by focusing on marker replacement, unlike generate or refresh.

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

Usage Guidelines4/5

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

The description clearly implies when to use the tool: when markdown contains '/toc' markers that need to be replaced with a TOC. However, it does not explicitly mention alternatives like markdown_generate_toc or markdown_refresh_toc or provide exclusion cases.

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

Deploy Server