Skip to main content
Glama

pdf_convert_excel

Convert Excel or CSV files into styled PDFs via semantic HTML, with CSS presets, custom CSS, page size, and orientation options.

Instructions

Convert Excel/CSV to styled PDF via semantic HTML

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": "<input>",
      "output": "<output>"
    },
    "name": "pdf_convert_excel"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to input file
outputYesPath to output PDF file
presetNoCSS preset (github, elegant, minimal, branded, compact)
page_sizeNoPage size format (e.g. A4, Letter)
custom_cssNoCustom CSS rules to apply
orientationNoPage orientation (portrait or landscape)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether the output file is overwritten, whether existing files are an error, what conversion fidelity to expect from the "semantic HTML" pipeline, or how custom_css interacts with preset. For a file-writing tool with zero annotation coverage this is a real gap.

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?

A single front-loaded sentence with no filler. The "via semantic HTML" clause adds a small amount of implementation context rather than padding, though the sentence is arguably too terse for a six-parameter mutation tool.

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?

All parameters are documented in the schema and there is no output schema to explain, so the minimum needed to invoke the tool is present. However, with no annotations and no output description, the agent lacks information about failure modes and output-file behavior.

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 all six parameters including preset values and page_size are already documented in the schema. The description only adds the notion of "styled" output via semantic HTML, which weakly signals the styling parameters but adds no format or precedence rules.

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: "Convert Excel/CSV to styled PDF". The input formats (Excel/CSV) implicitly distinguish it from siblings like pdf_convert_html and pdf_convert_markdown, though no sibling is named explicitly.

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 when-to-use guidance, no conditions for choosing this over pdf_convert_html or pdf_convert_markdown, and no prerequisites noted. The agent must infer that the tool applies only when the source is a spreadsheet.

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