Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Markdown to PDF

cc_md_to_pdf
Idempotent

Converts Markdown files to PDF using a headless Edge or Chrome browser, with automatic fallback to HTML when no browser is found.

Instructions

Converts Markdown to PDF using a headless browser (Edge/Chrome).

Args:

  • input_path (string): Path to the Markdown file

  • output_path (string): Path to the PDF output

  • title (string, optional): Document title

Uses the same Markdown parser as cc_md_to_html. Requires Edge or Chrome. Falls back to HTML if no browser is found.

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": {
      "input_path": "<input_path>",
      "output_path": "<output_path>"
    },
    "name": "cc_md_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoDocument title
input_pathYesMarkdown file
output_pathYesPDF output

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.8

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, idempotent=true, destructive=false), so the bar is lower. The description nonetheless adds genuinely non-obvious behavior: the browser dependency and the silent degradation to HTML when no browser is present — a real correctness caveat for an agent. It omits whether an existing output_path is overwritten and what the fallback path/return looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence and the closing behavioral notes are front-loaded and useful, but the Args block fully duplicates a schema that already has 100% description coverage, consuming roughly a third of the text without adding information.

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 two-required-param converter with annotations present and no output schema, the description covers inputs, the runtime prerequisite, and failure-mode behavior. The main residual gap is what the agent receives when the HTML fallback triggers, but the essentials for calling it correctly are present.

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 three properties are already documented. The Args block merely restates them ('Markdown file', 'PDF output', 'Document title') with no added syntax, format, or path-resolution detail, so the baseline 3 applies.

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 first sentence gives a specific verb+resource (converts Markdown to PDF) and names the exact mechanism (headless Edge/Chrome). It also explicitly relates itself to the sibling cc_md_to_html via the shared parser and the HTML fallback, so an agent can tell the two apart without opening either schema.

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 preprocessing requirement ('Requires Edge or Chrome') and the fallback condition ('Falls back to HTML if no browser is found') imply when this tool is viable, but there is no explicit statement of when to choose it over cc_md_to_html or what to do when the environment lacks a browser. Guidance is inferable rather than stated.

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