Skip to main content
Glama

Pressa - LaTeX to PDF

by io.github.pressa-dev
OverviewDiscussionsAdmin

Server Details

Compile LaTeX to PDF without installing TeX Live. No API key needed to start.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
pressa-dev/mcp
GitHub Stars
0
Server Listing
@pressa/mcp

TDQS

A5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly defined and scoped to compiling LaTeX to PDF, making selection unambiguous.

Naming Consistency5/5

A single tool named 'compile' is simple and directly describes the action. Since there is only one tool, there are no naming inconsistencies or mixed conventions to penalize.

Tool Count5/5

The server's purpose is narrowly defined as compiling LaTeX to PDF, which is exactly one operation. One tool is perfectly well-scoped for this domain; additional tools would add unnecessary surface area.

Completeness5/5

The compile tool fully covers the server's stated purpose. It handles errors with diagnostics, indicates preview/limits, and explicitly documents what it does not do, so there are no missing core operations within its narrow scope.

Available Tools

1 tool
compileCompile LaTeX to PDFAInspect

Compile LaTeX source into a PDF. Returns a PDF URL, page count and compile time.

USE THIS WHEN: you have LaTeX source (or a \documentclass) and no local pdflatex / TeX Live installation to run it with. This is that missing compiler, available over HTTP. Also use it whenever the user asks for a document where typesetting matters - an invoice, contract, report, letter, CV, certificate, or academic paper - since you can write the LaTeX yourself and compile it here.

DO NOT USE THIS TO: convert HTML to PDF, merge, split or compress existing PDF files, or extract text from a PDF. This compiles LaTeX source and nothing else.

No API key is required. Anonymous callers get a small number of compilations per day and failed attempts do not count, so you can iterate on your LaTeX for free. Send an API key in the Authorization header to raise the limits. With a key, a document over the plan's page or size limit still returns a PDF: preview: true, the first pages the plan allows, total_pages, and plan_required naming the plan that covers the whole document. Show the user the preview and relay warning; never drop pages silently.

IMPORTANT: This tool compiles LaTeX, NOT plain text. You must generate complete, valid LaTeX source yourself before calling it. Do not pass plain text, markdown or JSON directly - convert them to LaTeX first, and never ask the user to write LaTeX.

A minimal valid document is: \documentclass{article}\begin{document}\end{document}. Escape these in body text: % & $ # _ { } and backslash.

If compilation fails the response includes a diagnosis naming the cause and a concrete suggested fix, often a missing \usepackage. Apply it and call again yourself rather than showing the user a TeX log.

ParametersJSON Schema
NameRequiredDescriptionDefault
latexYesComplete LaTeX source, including \documentclass and \begin{document}...\end{document}.
compilerNoDefaults to pdflatex. Anonymous callers may only use pdflatex.

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (which only indicate open-world and non-read-only), the description discloses important behaviors: anonymous rate limits, failed compilations not counting, preview behavior with API keys, and automatic diagnosis on failure. It also warns that it compiles LaTeX only, not plain text. This fully covers behavioral context without contradicting annotations.

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?

The description is structured with clear headings and front-loaded purpose. Every sentence adds meaningful information—usage conditions, limits, error handling, and examples—without redundant fluff. The length is justified by the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all essential aspects: return values (PDF URL, page count, compile time), error diagnosis, preview behavior with keys, anonymous limits, and LaTeX syntax requirements. It is thorough enough for an agent to use correctly without further clarification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant value: it explains the latex parameter must be complete and valid, gives a minimal document example, lists escape characters, and clarifies compiler defaults and anonymous restrictions. This goes well beyond the schema's basic descriptions.

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 clearly states the verb and resource: 'Compile LaTeX source into a PDF' and lists the return values. With no sibling tools, it unambiguously identifies the operation. The opening sentence is specific and sets expectations precisely.

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

Usage Guidelines5/5

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

The description provides explicit 'USE THIS WHEN' and 'DO NOT USE THIS TO' sections, naming concrete scenarios and exclusions. It also explains when to prefer this over local compilation and when to avoid it for other PDF operations, giving clear routing guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedcompile

Related MCP Connectors

Related MCP Servers

Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources