overleaf-claude-mcp

Compile and read the log

overleaf_compile_log

Compile a LaTeX project and retrieve parsed errors and warnings to diagnose and resolve build issues.

Instructions

Compile the project and return parsed LaTeX errors and warnings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "overleaf_compile_log"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 19, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The description discloses the core side effect (compiling the project) and the output type (parsed errors and warnings). However, with no annotations, it does not explain other behavioral considerations such as whether compilation modifies files, whether it uses the current project or requires a projectId, or how failures are surfaced.

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 a single concise sentence with no filler. It front-loads the action and output, making it easy to parse.

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

Completeness2/5

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

The tool has one parameter, no annotations, and no output schema, so the description must do more work. It lacks parameter semantics, usage conditions, and any detail about the parsed output or error behavior, leaving the agent with an incomplete picture.

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

Parameters1/5

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

The only parameter, projectId, is not mentioned in the description, and schema description coverage is 0%. The phrase 'the project' vaguely suggests a project is involved, but the agent is given no information about how to populate projectId or whether it is optional.

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 tool compiles the project and returns parsed LaTeX errors and warnings. This distinguishes it from siblings like overleaf_compile (which presumably just compiles) and overleaf_read_file (which reads files without compiling).

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?

No explicit guidance is given on when to use this tool versus overleaf_compile or overleaf_read_file. The use case is only implied by the action itself, and there is no mention of prerequisites, project selection, or alternatives.

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