Higgs Hub

Create OneDrive folder

create_onedrive_folder

Create a folder in OneDrive under the given parent (defaults to the drive root). If the name is taken, it is created with a suffix rather than merged.

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": {
      "mailbox": "<mailbox>",
      "name": "<name>"
    },
    "name": "create_onedrive_folder"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`mailbox`	Yes	Email address of the connected Outlook/Microsoft 365 mailbox to act on. Call list_authorized_mailboxes to see available options.
`parentItemId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-destructive write, so safety is covered. The description adds a genuinely non-obvious behavioral trait beyond annotations: duplicate names are resolved with a suffix rather than merged, which prevents the agent from assuming an upsert/merge. It stops short of mentioning permission/auth requirements or error modes.

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 filler, with the scope/default front-loaded and the collision semantics immediately after. Every clause carries information an agent needs.

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 create operation with no output schema and no annotations covering the result, the description should at least indicate that a new folder (and presumably its ID) is returned so it can be used by rename_onedrive_item / move_onedrive_item. It also omits the mailbox-authorization prerequisite. Adequate but with real gaps.

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 coverage is only 33% (only 'mailbox' is documented), so the description has to compensate. It usefully explains that 'parentItemId' is optional and defaults to the drive root, and its collision note implicitly covers 'name', but it never says how to obtain a valid parent item ID or what format it takes.

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?

States a specific verb (Create) and resource (a folder in OneDrive), plus the scoping detail that the parent defaults to the drive root. Combined with the name, this clearly separates it from the sibling create_gdrive_folder / create_mail_folder tools.

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 intent is obvious enough that usage is implied, and the collision behavior ('created with a suffix rather than merged') tells the agent what happens if the folder already exists. However, there is no explicit when-to-use vs. alternatives guidance, no prerequisite about needing an authorized mailbox, and no pointer to list_onedrive_items for resolving a parent ID.

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

All Higgs Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?