Skip to main content
Glama

overleaf_create_project

Create a new Overleaf project with a blank main.tex, an example template, or by uploading a local folder or ZIP archive.

Instructions

Create a brand-new Overleaf project (blank, example, or uploaded from a local folder or .zip).

Args: project_name: Title for the new Overleaf project. source_path: Optional local directory path or .zip archive path to populate the new project. template: When source_path is omitted, create 'none' (basic main.tex) or 'example'. ignore_patterns: Optional glob patterns to skip when zipping a local directory.

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_name": "<project_name>"
    },
    "name": "overleaf_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateNonone
source_pathNo
project_nameYes
ignore_patternsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real behavior: a local directory is zipped before upload, ignore_patterns applies only in that zipping path, and template is only meaningful when no source is given. It omits what happens on a project-name collision, whether authentication must be established first, and whether any side effects or limits apply.

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 capability is front-loaded in one sentence and the Args block maps one line per parameter with no filler. Nothing is repeated from the schema verbatim and no sentence is wasted.

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 the mode-selection logic is covered. For a creation tool with zero annotations, however, the description should say what happens when the name already exists and whether a prior auth step is required, both of which remain unstated.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does: all four parameters are explained with semantics the schema does not convey, including that source_path accepts either a directory or a .zip, that template is the fallback when source_path is omitted, and that ignore_patterns only affects the directory-zipping case.

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 ('Create a brand-new Overleaf project') and enumerates the three ways it can be populated (blank, example, from a local folder or .zip). It is clear on its own, but it does not differentiate itself from sibling upload tooling such as overleaf_upload_folder, which could look like an alternative route to the same outcome.

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

Usage Guidelines3/5

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

There is conditional guidance inside the parameter notes ('When source_path is omitted, create none or example'), which tells the agent how to pick a mode, but no statement of when this tool should be chosen over overleaf_upload_folder or overleaf_git_sync, and no prerequisites such as authentication.

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