Skip to main content
Glama
Sign In
claucloverleaf

claucloverleaf

by SolthaX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

overleaf_rename

Rename a document, file, or folder in an Overleaf project to update its name in place without moving it.

Instructions

Rename a document, file or folder in place.

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>",
      "new_name": "<new_name>"
    },
    "name": "overleaf_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath in the project, e.g. 'main.tex' or 'chapters/intro.tex'.
projectYesProject id, Overleaf project URL, or exact project name.
new_nameYesNew name (no folder part).

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=false and openWorldHint=true, so the safety profile is partly covered. Beyond that, the description adds almost nothing: it does not say what happens on a name collision, whether an existing target is overwritten, or whether renaming a folder affects child paths.

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 zero filler, and the key distinction ('in place') is placed early. It is efficient, though its brevity borders on under-specification rather than deliberate economy.

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, has three fully documented required parameters, an output schema, and annotations covering safety, so the description does not need to explain return values. However, for a rename operation the collision/overwrite behavior and folder-rename effects are meaningful gaps an agent would want resolved before calling.

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 all three parameters are documented in the schema, including the note that new_name takes no folder part. The description only generalizes the 'path' target types (document/file/folder) and adds no format or constraint detail beyond the schema, so baseline 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?

States a specific verb (rename) and a concrete set of resources (document, file or folder), and the phrase 'in place' signals that the parent path does not change, which distinguishes it from the sibling overleaf_move. It stops short of naming that sibling explicitly, so an agent must infer the boundary.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as overleaf_move for relocating items or overleaf_write_file for content changes. The only hint is the embedded phrase 'in place', which is left for the agent to interpret.

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