Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Markdown to HTML

cc_md_to_html
Idempotent

Convert Markdown files to standalone styled HTML documents that print to PDF via a browser, using an input file, output path, and optional title.

Instructions

Converts Markdown to formatted HTML (printable as PDF).

Args:

  • input_path (string): Path to the Markdown file

  • output_path (string): Path to the HTML output

  • title (string, optional): Document title

Produces standalone HTML with CSS styling, printable as PDF via browser.

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_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoDocument title
input_pathYesMarkdown file
output_pathYesHTML 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

B3.4/5.0
Behavior4/5

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

Annotations already declare write behavior, idempotency and non-destructiveness, so the description only needs incremental context. It delivers that by describing the output artifact ('standalone HTML with CSS styling, printable as PDF via browser'), which tells the agent what file shape to expect. It misses whether an existing output_path is overwritten, but that is partially implied by idempotentHint=true.

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

Conciseness4/5

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

Front-loaded with purpose and output characteristics, and the closing sentence adds real value. The Args block duplicates the schema wholesale, which is waste, but the total length stays small.

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 simple file-producing converter with full schema coverage and no output schema, the description covers purpose and output format adequately. It stops short of the operational facts an agent would want before a write: whether directories are created, whether the output path is overwritten, and what happens on invalid Markdown.

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 schema already carries parameter meaning and the description's Args block largely restates it. It does add the 'optional' marker on title, but nothing else about path semantics, creation behavior, or relative vs absolute paths.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource pair ('Converts Markdown to formatted HTML') plus the output artifact, which is clear on its own. It does not explicitly distinguish itself from near neighbors like cc_md_to_pdf or cc_convert_format; the PDF remark actually invites confusion about which tool to pick for PDF output.

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

Usage Guidelines2/5

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

There is no guidance about when to use this versus cc_md_to_pdf or cc_convert_format, which live in the same sibling set. Usage is only inferable from the verb, and the mention that output is 'printable as PDF' could actively mislead an agent choosing between conversion targets.

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