Skip to main content
Glama

rename

Change a file or folder’s name or location on a host, enabling you to reorganize or move assets over an SSH connection.

Instructions

Rename or move a file or folder on a host.

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": {
      "host": "<host>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
hostYes

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?

No annotations are provided, so the description carries the full behavioral burden and it discloses almost nothing: it does not say whether the target is overwritten, whether folders move recursively, whether permissions are required, or whether the operation is atomic. For a mutating filesystem operation on a remote host this is a significant gap.

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 tight sentence with the verb and scope front-loaded and no filler. Its brevity is a virtue structurally, even though the content it omits is penalized elsewhere.

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?

For a three-parameter required mutation tool with no annotations, no output schema, and zero schema coverage, the description is too thin to call correctly. Overwrite behavior, path conventions, and error/permission conditions are all missing.

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 0%, so the description should compensate; it does not, but the parameter names from/to/host are largely self-explanatory (source path, destination path, target host). A 3 reflects that the intent is readable from the names even with no added semantics such as path format or whether paths are absolute.

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 pair (rename/move) and a specific resource (file or folder) plus the scope 'on a host'. An agent can distinguish it from siblings like remove, make_dir, and write_file, though the description never names an alternative explicitly.

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?

The phrase 'rename or move' implies the two use cases, but there is no guidance on when to prefer this over download/upload plus removal, no prerequisites, and no statement of what happens if the destination already exists. The agent must infer all selection logic.

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