Skip to main content
Glama
Sign In
claucloverleaf

claucloverleaf

by SolthaX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

overleaf_download_pdf

Destructive

Compile an Overleaf project and save its output PDF to a local path, optionally overwriting an existing file.

Instructions

Compile the project and save the resulting PDF locally.

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": {
      "project": "<project>",
      "output_path": "<output_path>"
    },
    "name": "overleaf_download_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject id, Overleaf project URL, or exact project name.
overwriteNoReplace the file if it already exists.
output_pathYesLocal .pdf path (under the working directory).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: it does not explain that an existing file may be replaced, that compilation is a remote/network operation, or what occurs when the project fails to compile. For a destructive, open-world mutation, this leaves meaningful gaps.

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 the action sequence in the right order and no wasted wording. It is efficient, though its brevity contributes to the missing behavioral detail elsewhere.

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?

An output schema exists, so return values need not be described, and all parameters are documented in the schema. However, for a destructive, open-world tool that overlaps with overleaf_compile, the description should at least clarify the sibling boundary and the overwrite/destructive implication, which it omits.

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 project (id/URL/name), output_path, and overwrite are all documented in the schema. The description adds no extra meaning such as path restrictions or overwrite implications, so the baseline of 3 applies.

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?

The description gives a concrete verb chain ('compile the project and save the resulting PDF locally'), which tells an agent exactly what happens. The mention of saving the PDF locally implicitly separates it from the sibling overleaf_compile, but the distinction is never made explicit.

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 and no reference to the closely related overleaf_compile sibling, so an agent must infer that this tool is the one that persists the compiled artifact. No prerequisites, no note on what happens when compilation fails, and no exclusions.

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

Deploy Server

Other Tools