Skip to main content
Glama
Sign In
claucloverleaf

claucloverleaf

by SolthaX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

overleaf_create_folder

Create a folder, including any missing parent folders, in an Overleaf project to organize files.

Instructions

Create a folder (and 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": {
      "project": "<project>",
      "path": "<path>"
    },
    "name": "overleaf_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath in the project, e.g. 'main.tex' or 'chapters/intro.tex'.
projectYesProject id, Overleaf project URL, or exact project name.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds one genuinely useful behavioral detail — that missing parent folders are created automatically — but says nothing about idempotency when the folder exists, permission requirements, or side effects on the project tree.

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 short sentence with zero filler and the key detail (parent creation) front-loaded. It is arguably too terse for a mutation tool, but every word present earns its place.

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?

The tool is simple (2 fully documented required params, an output schema, and annotations covering safety), so the burden is modest and largely met. Still missing is what an agent would want to know before mutating a project: behavior on an existing folder and whether 'path' refers to a folder or file namespace.

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 both 'path' and 'project' are already documented in the schema, establishing the baseline of 3. The description does not clarify whether 'path' here is a folder path (the schema's example values are file paths such as 'main.tex'), which is the one semantic gap worth closing.

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 specific verb and resource ("Create a folder") plus a scope qualifier ("and any missing parents"), which lets an agent distinguish it from sibling tools like overleaf_write_file or overleaf_move. It stops short of naming any sibling explicitly, which keeps it from a 5.

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 guidance on when to use this versus alternatives such as overleaf_create_project (which may also create folders) or overleaf_write_file (which may implicitly create paths). No prerequisites, no note about what happens if the folder already exists, 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