Skip to main content
Glama

graph_invite_to_file

Invite people by email to a OneDrive file or folder, granting read or write access and optionally sending an invitation message through Microsoft Graph.

Instructions

Invite people to a file or folder by email.

Args: item_id: The file or folder ID to share. emails: Email addresses of the people to invite. role: Access to grant: "read" or "write" (default "read"). send_email: Whether Graph should email the invitation (default false). message: Optional message to include with the invitation. drive_id: Drive ID to act on. Empty targets your own OneDrive.

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>",
      "emails": "<emails>"
    },
    "name": "graph_invite_to_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoread
emailsYes
item_idYes
messageNo
drive_idNo
send_emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it never states that this is a mutating operation, what permission level the caller needs (owner vs. member), what happens if the invitee already has access, or whether external recipients are allowed. It only discloses parameter-level defaults like send_email=false, which is far short of what an agent needs before granting access.

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 purpose sentence is front-loaded and the Args block is scannable with one line per parameter. Some redundancy exists where defaults are restated from the schema, but nothing is wasteful enough to obscure the content.

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?

Six parameters with zero annotation coverage and no output schema demand more than this: no return value description, no permission prerequisites, and no error/edge-case behavior (already-shared users, invalid emails). The thorough parameter documentation partially makes up for it, leaving it adequate but incomplete.

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 description coverage is 0%, but the description compensates by documenting all six parameters, including the role enum values, both defaults, and the non-obvious semantics of an empty drive_id. The only shortfall is that 'message' and 'send_email' interplay is not explained.

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?

The first line names a specific verb and resource: 'Invite people to a file or folder by email,' which tells an agent exactly what the operation does. It does not, however, distinguish itself from the sibling graph_share_file, leaving ambiguity about which to choose for granting access.

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?

Usage is implied by the sharing context, and 'drive_id: Empty targets your own OneDrive' gives a useful selection cue. There is no explicit when-to-use/when-not guidance and no mention of graph_share_file as an alternative for permission grants.

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