Skip to main content
Glama

graph_create_folder

Creates a folder in OneDrive from a folder name and optional parent folder ID, so you can organize files under a chosen directory or the drive root.

Instructions

Create a folder in OneDrive.

Args: folder_name: Name of the new folder. parent_folder_id: Parent folder ID. Empty for the drive root.

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": {
      "folder_name": "<folder_name>"
    },
    "name": "graph_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_nameYes
parent_folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It never says what happens if the folder name already exists, what permissions are required, or whether the operation is idempotent. For a mutating tool with zero annotation coverage, 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?

The one-line purpose is front-loaded and the args block is compact with no wasted prose. The Args section is slightly verbose in form but not padded.

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?

For a simple two-parameter creation tool with no output schema, the essentials are covered. However, it omits what the call returns (e.g., the new folder ID) and collision/permission behavior, which an agent would need before invoking it.

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 must compensate, and it does document both parameters. 'Empty for the drive root' adds real meaning beyond the schema's default value, though the rest largely restates parameter names.

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 and resource, 'Create a folder in OneDrive', which is enough to distinguish it from mail-folder creation among the siblings. It doesn't explicitly name a sibling alternative, but the OneDrive scope is concrete.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as graph_create_mail_folder. The agent must infer usage entirely from the verb.

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