Skip to main content
Glama
Sign In
md-vision

md-vision

by japlete
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Index markdown headings

index_md
Read-onlyIdempotent

Index headings in markdown files, URLs, or folders. Returns frontmatter and a TSV table of headings with line numbers, image count, and character count.

Instructions

Index headings in a markdown file, URL, or local folder. Returns frontmatter (if any) and a TSV table of headings, line_start, n_images, char_count; use read_md_with_images to read specific content.

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": {
      "uri": "<uri>"
    },
    "name": "index_md"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesLocal path, HTTP(S) URL, or local folder to index for markdown headings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds detail about return format (frontmatter, TSV table) without contradicting annotations.

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?

Two sentences: first clearly states the purpose, second adds output details and sibling distinction. No wasted words.

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

Completeness5/5

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

For a simple tool with one parameter, full annotations, and no output schema, the description covers purpose, usage guidelines, and return type adequately.

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 has 100% coverage for the single parameter 'uri' with a clear description. The tool description does not add significant new meaning beyond the schema.

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?

Description states verb 'Index' on resource 'markdown headings', specifies sources (file, URL, folder), and differentiates from sibling tool read_md_with_images by indicating the latter is for reading content.

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

Usage Guidelines5/5

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

Explicitly indicates when to use this tool (to index headings) and provides an alternative for reading content: 'use read_md_with_images to read specific content.'

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