Skip to main content
Glama
Sign In
stela-mcp

stela-mcp

by Sachin-Bhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_file

Move or rename files and directories to a new path within allowed directories. Prevents accidental overwrites by failing when destination exists.

Instructions

Move or rename files and directories. Fails if the destination already exists.Both source and destination must resolve within allowed directories:

  • /app

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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource path
destinationYesDestination path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It correctly notes failure if destination exists and path restrictions, but omits other important traits such as atomicity, whether overwrite is possible under any condition, permissions required, or return value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words. Front-loaded with the primary action. Efficiently conveys core information.

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?

Given no output schema and no annotations, the description is adequate for a simple move operation but lacks details on error conditions (e.g., source not found, permissions), return values, or confirmation. Completeness is moderate.

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?

Although the input schema already describes both parameters as paths, the description adds the valuable constraint that both must resolve within allowed directories, which is not explicit in the schema.

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?

The description clearly states the verb 'move' and 'rename' with 'files and directories', and specifies a key condition (fails if destination exists) and path restriction, distinguishing it from siblings like copy or delete.

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

Usage Guidelines3/5

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

The description implies use for moving/renaming but provides no explicit guidance on when to use this tool over alternatives like copy (for duplication) or write (for new files), nor does it mention prerequisites or when not to use it.

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