Skip to main content
Glama
jathinkolla

Pandoc Document Conversion

by jathinkolla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UV_PUBLISH_TOKENNoYour token used for publishing to PyPI
UV_PUBLISH_PASSWORDNoYour password for publishing to PyPI
UV_PUBLISH_USERNAMENoYour username for publishing to PyPI

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
convert-contentsA

Converts content between different formats. Transforms input content from any supported format into the specified output format.

šŸšØ CRITICAL REQUIREMENTS - PLEASE READ:

  1. PDF Conversion:

    • You MUST install TeX Live BEFORE attempting PDF conversion:

    • Ubuntu/Debian: sudo apt-get install texlive-xetex

    • macOS: brew install texlive

    • Windows: Install MiKTeX or TeX Live from https://miktex.org/ or https://tug.org/texlive/

    • PDF conversion will FAIL without this installation

  2. File Paths - EXPLICIT REQUIREMENTS:

    • When asked to save or convert to a file, you MUST provide:

      • Complete directory path

      • Filename

      • File extension

    • Example request: 'Write a story and save as PDF'

    • You MUST specify: '/path/to/story.pdf' or 'C:\Documents\story.pdf'

    • The tool will NOT automatically generate filenames or extensions

  3. File Location After Conversion:

    • After successful conversion, the tool will display the exact path where the file is saved

    • Look for message: 'Content successfully converted and saved to: [file_path]'

    • You can find your converted file at the specified location

    • If no path is specified, files may be saved in system temp directory (/tmp/ on Unix systems)

    • For better control, always provide explicit output file paths

Supported formats:

  • Basic formats: txt, html, markdown

  • Advanced formats (REQUIRE complete file paths): pdf, docx, rst, latex, epub

āœ… CORRECT Usage Examples:

  1. 'Convert this text to HTML' (basic conversion)

    • Tool will show converted content

  2. 'Save this text as PDF at /documents/story.pdf'

    • Correct: specifies path + filename + extension

    • Tool will show: 'Content successfully converted and saved to: /documents/story.pdf'

āŒ INCORRECT Usage Examples:

  1. 'Save this as PDF in /documents/'

    • Missing filename and extension

  2. 'Convert to PDF'

    • Missing complete file path

When requesting conversion, ALWAYS specify:

  1. The content or input file

  2. The desired output format

  3. For advanced formats: complete output path + filename + extension Example: 'Convert this markdown to PDF and save as /path/to/output.pdf'

Note: After conversion, always check the success message for the exact file location.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'convert-contents' has a single, clearly defined purpose: converting content between formats.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'convert-contents' follows a clear verb_noun pattern, but with no other tools to compare, consistency is not an issue.

Tool Count2/5

The server is named 'Pandoc Document Conversion' and has only one tool. For a document conversion domain, a single tool is too few to provide comprehensive coverage, as it lacks specialized tools for different conversion scenarios or formats, making it feel thin and under-scoped.

Completeness2/5

The tool surface is severely incomplete for the domain of document conversion. While 'convert-contents' handles format conversion, there are obvious gaps such as tools for listing supported formats, validating input, batch processing, or handling metadata, which are common in such systems.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources