Skip to main content
Glama
reeinharddd

snapmcp

by reeinharddd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

capture_terminal

Generate styled terminal screenshots from text lines with authentic theme colors. Use it for CLI tutorials, command output documentation, and terminal guides.

Instructions

Generate a styled terminal screenshot from text lines with real terminal theme colors. Automatically detects your terminal theme (Kitty, GNOME, Alacritty, WezTerm, etc.) for authentic prompt colors. Use for CLI tutorials, command output documentation, and terminal-based guides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesYesLines to render. Prefix command prompts with '$ ' (or '# ' for root) for syntax-colored prompts. Other lines are rendered as output. Maximum 1000 lines.
titleYesWindow title shown in the terminal title bar (e.g., 'bash', 'zsh', 'git log')
outputNoOutput filename (default: auto-generated as 'terminal-<timestamp>.png' or '.jpeg' based on SNAPMCP_FORMAT). Include extension to override format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.3.4
    • changedInput schema / properties / lines / description
      Previous value: -"Lines to render. '$ ' prefix = command prompt, others = output"New value: +"Lines to render. Prefix command prompts with '$ ' (or '# ' for root) for syntax-colored prompts. Other lines are rendered as output. Maximum 1000 lines."
    • addedInput schema / properties / lines / maxItems
      Added value: +1000
    • changedInput schema / properties / output / description
      Previous value: -"Output filename (default: auto-generated)"New value: +"Output filename (default: auto-generated as 'terminal-<timestamp>.png' or '.jpeg' based on SNAPMCP_FORMAT). Include extension to override format."
    • changedInput schema / properties / title / description
      Previous value: -"Window title shown in the terminal title bar"New value: +"Window title shown in the terminal title bar (e.g., 'bash', 'zsh', 'git log')"
    • addedInput schema / properties / title / maxLength
      Added value: +100
  2. First observedv2.3.2

TDQS

A4.2/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 full burden of behavioral disclosure, and it delivers a genuinely non-obvious trait: automatic theme detection (Kitty, GNOME, Alacritty, WezTerm, etc.) that determines prompt colors. It doesn't disclose the return value or file-write side effects in the description, but the core generation behavior is transparent.

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?

Three sentences, each earning its place: core function, behavioral nuance, and use cases. The purpose is front-loaded in sentence one with no filler or redundant restatement of schema content.

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 modest-complexity tool with fully documented parameters, the description covers purpose, usage, and the key behavioral quirk. The main gap is that there is no output schema and the description never states what the tool returns (e.g., a file path or URL), though the output parameter's filename semantics imply a saved artifact.

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% — lines, title, and output each have inline documentation including the '$ '/ '# ' prompt-prefix rule and filename defaults, so the schema already carries the parameter semantics. The description adds theme-detection context that influences rendering but no per-parameter meaning, matching the baseline of 3.

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 opens with a specific verb and resource — "Generate a styled terminal screenshot from text lines" — and the terminal focus clearly differentiates it from capture_markdown, capture_code, and capture_html siblings. The phrase "with real terminal theme colors" further pins down the artifact type and rendering behavior.

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 closing sentence gives explicit use cases: "Use for CLI tutorials, command output documentation, and terminal-based guides." It provides clear context for when to select this tool, but it doesn't name alternatives or state when not to use it, so it stops short of full exclusion guidance.

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