Skip to main content
Glama

rename_file

Renames a file on disk without changing the item's displayed name or extension; refuses canvas files to prevent broken references.

Instructions

Rename the file on disk. This changes the filename, not the item's name — use describe_item for that. Most of the time describe_item is what you want: the name is what the app displays, and a camera filename is only worth changing when it is actively misleading.

REFUSES for a file that is on a canvas. Renaming one would leave every canvas element pointing at nothing; the app's own rename fixes those up as it goes, and only the app can, so do it there.

The extension is kept and cannot be changed — it describes the bytes, not the name.

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": {
      "path": "<path>",
      "name": "<name>"
    },
    "name": "rename_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new filename, without an extension.
pathYesThe item, as search_inspo reports it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses a hard refusal for canvas-attached files with the reason (canvas elements would dangle), and that the extension is preserved and immutable. It stops short of stating permissions needed, whether a rename is reversible, or what the call returns, so it is rich but not exhaustive.

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 action, then routing guidance, then the refusal, then the extension rule — each in its own short block. The prose is slightly chatty ("Most of the time describe_item is what you want"), but that sentence earns its place by steering the agent away from the common wrong call.

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?

For a two-parameter mutation tool with no annotations and no output schema, the description covers the risky parts an agent most needs: the refusal condition and the extension invariant. Only the return value and permission/authorization expectations are unaddressed, which are minor for this complexity.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: the extension is kept and cannot be changed, which constrains how the `name` argument should be formed even though the schema only says "without an extension". It does not restate the `path` convention, which the schema already handles.

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?

Opens with a specific verb+resource ("Rename the file on disk") and immediately disambiguates the scope: filename on disk, not the item's display name. It names describe_item as the tool for the other sense of "name", so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ("a camera filename is only worth changing when it is actively misleading"), when-not-to-use ("Most of the time describe_item is what you want"), and a hard refusal case (files on a canvas). The alternative and the condition that selects it are both stated, not inferred.

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