overleaf-claude-mcp

Create a folder

overleaf_create_folder

Create a new folder within an Overleaf project, automatically generating any missing parent folders to organize LaTeX files.

Instructions

Create a folder, including any missing parents.

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": {
      "folderPath": "<folderPath>"
    },
    "name": "overleaf_create_folder"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	No
`folderPath`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 19, 2026

TDQS

C2.8/5.0

Behavior2/5

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

The description adds one behavioral trait ('including any missing parents'), but without annotations, it must carry the full burden of disclosure. It does not state what happens if the folder already exists, whether the operation is recursive or idempotent, or any permission requirements.

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?

The description is a single sentence with no fluff, but the first part 'Create a folder' directly repeats the title. Still, the 'including any missing parents' addition earns its place, making it appropriately concise for the tool's simplicity.

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 no annotations, no output schema, and no schema descriptions, so the description is the sole documentation. It covers the core action but fails to explain parameter roles, expected return values, or error behavior, leaving the overall context incomplete.

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?

With 0% schema description coverage and no parameter documentation in the description, the meanings of 'folderPath' and 'projectId' are left entirely to the agent's inference. The description only says 'Create a folder' and provides no mapping to the parameters.

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 'Create a folder, including any missing parents' uses a clear verb and resource, and the 'including any missing parents' detail distinguishes it from any hypothetical simple folder creation. No sibling tool is for creating folders, so the purpose is unambiguous.

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 guidance is provided about when to use this tool versus alternative approaches or in which context (e.g., project selection). The only implicit usage is that it creates folders, but no exclusions or comparisons are mentioned.

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