Skip to main content
Glama
ftaricano

mcp-onedrive-sharepoint

by ftaricano

sync_folder

Synchronize a local folder with OneDrive or SharePoint bidirectionally, with conflict resolution and file pattern filters.

Instructions

Synchronize a local folder with OneDrive/SharePoint (bidirectional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localPathYesLocal folder path to sync
remotePathYesRemote folder path in OneDrive/SharePoint
siteIdNoSharePoint site ID (optional)
siteNoKnown SharePoint site alias or canonical URL
siteUrlNoCanonical SharePoint site URL (optional alternative to siteId)
driveIdNoDrive ID for a specific document library (optional)
directionNoSync directionbidirectional
conflictResolutionNoHow to resolve conflictsnewer
includePatternsNoFile patterns to include (e.g., ["*.docx", "*.xlsx"])
excludePatternsNoFile patterns to exclude (e.g., ["*.tmp", "~*"])
deleteOrphansNoDelete files that exist only on one side
Behavior2/5

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

No annotations provided; description is minimal and doesn't disclose behavioral traits beyond 'bidirectional', such as side effects, long-running nature, or permission requirements.

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?

Single sentence is efficient and front-loaded with purpose, but for a complex tool with 11 parameters, additional context could be warranted without being overly verbose.

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?

Given the tool's complexity, the description is too brief; it omits details like recursive sync, parameter behaviors, and return information, leaving the agent underinformed.

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 baseline is 3; description adds no additional parameter meaning beyond what the schema already provides.

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?

The description clearly states it synchronizes a local folder with OneDrive/SharePoint and specifies bidirectional, which distinguishes it from one-way upload/download tools among siblings.

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?

No guidance on when to use this tool versus alternatives like upload_file or download_file; lacks context for selecting direction or conflict resolution.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ftaricano/mcp-onedrive-sharepoint'

If you have feedback or need assistance with the MCP directory API, please join our Discord server