Skip to main content
Glama
Hermoso

Hermoso

Official

Share a OneDrive file as a link

share_onedrive_file
DestructiveIdempotent

Create view, edit, or embed sharing links for OneDrive files and folders, with anonymous, organization, or invited-user access plus optional expiration and password.

Instructions

Create a SHARING LINK to a OneDrive file or folder (fileId from list_onedrive_files): type view (read-only, default), edit, or embed (an link, personal OneDrive only); scope anonymous (anyone with the link, default), organization (work or school OneDrive only) or users (only people you invite); optional expiresAt (date or ISO) and password (on a personal OneDrive both need a Microsoft 365 subscription; the refusal says so). An ANONYMOUS EDIT link lets anyone holding it change or delete the file, so it needs confirm:true after you show the user that; every other link is created straight away. If Hermoso already made the same kind of link, OneDrive returns that one and the reply says it was reused. Read back from the item's permission list. 0 credits. Needs OneDrive connected.

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": {
      "fileId": "<fileId>"
    },
    "name": "share_onedrive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoview (default), edit, or embed (personal OneDrive only)
scopeNoanonymous (default, anyone with the link), organization (work or school), or users (invited people only)
fileIdYesOneDrive file or folder id from list_onedrive_files
confirmNorequired for an anonymous edit link
passwordNopersonal OneDrive with Microsoft 365
expiresAtNoe.g. 2026-11-30 or 2026-11-30T17:00:00Z

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.465

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that an anonymous edit link lets anyone change or delete the file, that a confirm flag is required only in that case, that identical links are reused rather than recreated, that password/expiresAt on personal OneDrive need a Microsoft 365 subscription with a refusal message, that it costs 0 credits, and that OneDrive must be connected. This substantially enriches what destructiveHint and idempotentHint alone convey.

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?

Front-loads the core action and the most consequential warning sits mid-paragraph; every sentence carries information (defaults, confirm gate, reuse, cost, connection). It is dense, semicolon-heavy prose that could be broken into bullets for faster scanning, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no output schema, the description covers the risk profile, prerequisites, defaults, cost, deduplication behavior, and where to verify the resulting permission. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds conditional semantics the schema does not: embed is personal-only, organization scope is work/school-only, and password/expiresAt require a subscription on personal accounts. Only the exact confirm interaction and expiresAt formats are left to 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?

States a specific verb and resource ('Create a SHARING LINK to a OneDrive file or folder') and disambiguates from siblings by naming list_onedrive_files as the source of fileId and pointing at the item's permission list for read-back. An agent can distinguish it from onedrive_file_permissions or get_onedrive_file immediately.

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

Usage Guidelines4/5

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

Gives explicit defaults (view, anonymous), an explicit prerequisite gate (confirm:true only for anonymous edit links, after showing the user), and points to list_onedrive_files for the id. It stops short of naming the sibling tool to use for listing or revoking existing links, which is left implicit.

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