Skip to main content
Glama
Sign In
m365-organizer

m365-organizer

by Denovarix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

drive_move

Moves a OneDrive item to a destination path and creates the path when missing; optionally renames the item during the move.

Instructions

Move a OneDrive item into dest_path (created if missing).

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": {
      "item_id": "<item_id>",
      "dest_path": "<dest_path>"
    },
    "name": "drive_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
new_nameNo
dest_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It does mention that dest_path is created if missing, but it omits important mutation details such as overwrite behavior, permission requirements, and what happens to existing items.

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?

The description is a single front-loaded sentence with no wasted words. It states the core action and the most important destination behavior immediately.

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 mutation tool with no annotations and no schema descriptions, this is too sparse. The output schema covers return values, but the description still leaves new_name unexplained and omits overwrite and permission behavior.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to compensate for all three parameters. It clarifies dest_path auto-creation and references item_id indirectly, but never explains new_name or gives format/meaning for item_id and dest_path.

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 gives a specific verb and resource: 'Move a OneDrive item.' The destination path behavior is also stated, making the operation clearly distinct from sibling tools like drive_list and drive_create_folder.

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?

It states the operation but gives no guidance about when to use it versus alternatives or when not to use it. The only additional context is that dest_path is created if missing, which is behavioral rather than usage guidance.

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