Skip to main content
Glama
Sign In
snapmcp

snapmcp

by reeinharddd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

capture_markdown

Render Markdown into a styled document screenshot with GitHub-flavored tables, task lists, code highlighting, Mermaid diagrams, and HTML support.

Instructions

Render Markdown as a styled document screenshot using GitHub-flavored Markdown. Supports tables, task lists, code blocks with syntax highlighting, mermaid diagrams (as text), and HTML. Renders with the configured Shiki theme and document styling. Maximum input 200KB.

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": "capture_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoDocument title shown in the window title bar and as H1 if not present in markdown.document
outputNoOutput filename (default: auto-generated as 'markdown-<timestamp>.png' or '.jpeg' based on SNAPMCP_FORMAT). Include extension to override format.
markdownYesMarkdown content to render. Supports GFM: tables, task lists, fenced code blocks, strikethrough, autolinks. Maximum 200KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.3.4
    • changedInput schema / properties / markdown / description
      Previous value: -"Markdown content to render"New value: +"Markdown content to render. Supports GFM: tables, task lists, fenced code blocks, strikethrough, autolinks. Maximum 200KB."
    • addedInput schema / properties / markdown / maxLength
      Added value: +200000
    • changedInput schema / properties / output / description
      Previous value: -"Output filename (default: auto-generated)"New value: +"Output filename (default: auto-generated as 'markdown-<timestamp>.png' or '.jpeg' based on SNAPMCP_FORMAT). Include extension to override format."
    • changedInput schema / properties / title / description
      Previous value: -"Document title"New value: +"Document title shown in the window title bar and as H1 if not present in markdown."
    • addedInput schema / properties / title / maxLength
      Added value: +100
  2. First observedv2.3.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses significant traits: rendering with a configured Shiki theme, support for HTML, the specific limitation that mermaid diagrams are rendered as text, and a maximum input size of 200KB. It does not mention output-file side effects or return values, which keeps it from a 5.

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 three sentences and front-loads the core purpose before adding supporting details. Every sentence contributes either a capability, a rendering behavior, or a constraint, with no fluff or redundant restatement of the tool name.

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 rendering tool with no output schema and no annotations, the description covers input constraints and rendering features well but omits what the tool returns or where the output screenshot is written. It is useable but not fully self-sufficient for an agent that needs to consume the produced artifact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema. It reveals mermaid-as-text behavior, HTML support, and Shiki theme rendering, which directly affect how the markdown parameter's content will be interpreted and displayed.

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 opening sentence, 'Render Markdown as a styled document screenshot using GitHub-flavored Markdown,' names a specific action, resource, and output artifact. It further differentiates itself from siblings by listing supported features (tables, task lists, code blocks, mermaid as text, HTML) that are unique to Markdown rendering.

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 when Markdown content needs to become a styled screenshot, but it never explicitly states when to prefer this over alternatives like capture_html or capture_code, nor does it explain when not to use it. The context is clear but exclusions and sibling routing are left to inference.

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