Skip to main content
Glama

rename_entity

Destructive

Rename or move files, documents, and folders in an Overleaf project by specifying a new name or destination path; creates missing folders and asks for confirmation before writing.

Instructions

Rename a file, document, or folder within an Overleaf project, or move it into another folder. new_name without a slash renames in place. A path such as "chapters/intro.tex" moves the entity into that folder under that name, creating missing folders. A path ending in a slash, such as "chapters/", moves it and keeps the name; "/" is the project root. Nothing is written when the destination already exists, the source is not found, or a folder would move into itself. Asks the user to confirm in the MCP client before writing.

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_id": "<project_id>",
      "remote_path": "<remote_path>",
      "new_name": "<new_name>"
    },
    "name": "rename_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYesNew name (renames in place), or a destination path: "folder/name.tex" moves and renames, "folder/" moves and keeps the name, "/" is the project root
project_idYesThe Overleaf project ID
remote_pathYesCurrent path of the file/document/folder within the project

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.3
    • changedInput schema / properties / new_name / description
      Previous value: -"New filename (basename only, not a full path)"New value: +"New name (renames in place), or a destination path: \"folder/name.tex\" moves and renames, \"folder/\" moves and keeps the name, \"/\" is the project root"
    • changedInput schema / properties / remote_path / description
      Previous value: -"Current path of the file/document within the project"New value: +"Current path of the file/document/folder within the project"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: missing folders are created, conflicting destinations and missing sources cause no write, and the MCP client prompts the user to confirm before writing. That confirmation detail is valuable given destructiveHint=true. It stops short of saying what a failure looks like to the caller.

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?

Front-loaded with the core action and the three path forms, then the failure conditions and confirmation note. Every sentence carries information; the density is high but still readable, with only minor overlap between the description and the new_name schema text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A three-parameter mutation tool with no output schema is well covered: path grammar, implicit folder creation, no-op conditions, and the confirmation step are all stated. The only gap is what the tool returns on success or how errors are surfaced.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description adds concrete semantics the schema only summarizes: slashless means in-place rename, 'chapters/intro.tex' means move-and-rename, 'chapters/' means move-and-keep, '/' means root. Worked examples make the path grammar unambiguous.

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?

States a specific verb (rename/move) and resource (file, document, folder in an Overleaf project) and immediately distinguishes the two behaviors: in-place rename versus move-with-rename versus move-keeping-name. An agent can distinguish this from delete_entity or push_file from the description alone.

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

Usage Guidelines4/5

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

Gives explicit interpretation rules for new_name, including the trailing-slash and project-root '/' conventions, plus the no-write conditions (destination exists, source missing, self-move). It doesn't route to siblings such as plan_project_renames or delete_entity, so alternative selection is left implicit.

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