Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

files

Manage OneDrive and SharePoint content by listing, uploading, downloading, searching, sharing, moving, copying, and deleting items or creating folders.

Instructions

Manage OneDrive and SharePoint files: list, get, upload, download, cleanup_download, delete, share, search, move, copy, create_folder

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": {
      "operation": "<operation>"
    },
    "name": "files"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFolder name
pathNoFile path (alternative to fileId, or local temp path for cleanup_download)
typeNoShare permission type
queryNoSearch query
scopeNoShare scope
fileIdNoFile or folder ID
siteIdNoSharePoint site ID
contentNoFile content to upload
driveIdNoDrive ID (required for SharePoint files; returned by search as DriveID)
newNameNoNew name for file/folder
fileNameNoName for uploaded file
folderIdNoFolder ID to list contents
parentIdNoParent folder ID
passwordNoPassword for shared link
fileTypesNoFile types to filter (e.g., ['docx', 'pdf'])
operationYesThe operation to perform
maxResultsNoMaximum number of results
parentPathNoParent folder path
recipientsNoEmail addresses to share with
searchScopeNoSearch scope: 'me' (OneDrive only), 'sites' (SharePoint only), 'all' (both). Default: 'all'
contentBase64NoStrict RFC 4648 base64 for binary file content; mutually exclusive with content
destinationIdNoDestination folder ID
conflictBehaviorNoHow to handle naming conflicts
expirationDateTimeNoExpiration for shared link

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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, and it does not state that delete/cleanup_download are destructive or irreversible, what cleanup_download actually removes, where downloads land, or what permissions sharing requires. Only the bare operation names hint at the mutation profile, which is insufficient for a tool containing delete and move.

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?

A single front-loaded sentence with the resource first and the operation list second, so an agent gets the key facts immediately. The operation enumeration is largely redundant with the schema enum, which keeps it from a 5.

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 an 11-operation, 24-parameter mega-tool with no annotations and no output schema, the description gives no guidance on which parameters apply to which operation or what each returns. That mapping is the single most important thing an agent needs here and it is entirely absent.

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 100%, so every one of the 24 parameters is already documented in the schema, and the description adds no parameter-to-operation mapping or syntax detail. The operation list merely restates the 'operation' enum, so baseline 3 applies rather than a higher score.

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 description names the resource (OneDrive and SharePoint files) and a specific verb ('Manage'), then enumerates the concrete operations it supports. That lets an agent recognize the file-management tool without opening the schema, though the verb 'Manage' is generic and nothing separates it from the sibling 'search' tool.

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 or when-not-to-use guidance, no mention of the 'search' sibling that overlaps with the search operation, and no prerequisites such as required driveId for SharePoint. The operation list implies capability but gives no selection criteria.

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