Skip to main content
Glama
ftaricano

mcp-onedrive-sharepoint

by ftaricano

excel_operations

Read, write, and apply formulas to Excel workbooks stored in OneDrive or SharePoint. Supports operations like reading ranges, writing data, adding worksheets, creating tables, and generating charts.

Instructions

Perform operations on Excel workbooks (read, write, formulas)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdNoExcel file item ID
itemPathNoAlternative: Excel file path
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)
operationYesOperation to perform
worksheetNoWorksheet nameSheet1
rangeNoCell range (e.g., "A1:C10")
valuesNoValues to write (2D array of cell values)
formulasNoFormulas to set (2D array of formula strings)
tableNameNoName for new table
hasHeadersNoWhether table has headers
chartTypeNoChart type to create
useSessionNoUse persistent session for better performance
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It fails to disclose behavioral traits such as whether operations are destructive, authentication needs, rate limits, or session behavior beyond mentioning 'useSession'. The description lacks essential transparency.

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, front-loaded with key operations, no fluff. However, for a multi-operation tool, more structured listing would improve usability.

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?

With 15 parameters and 8 enum operations, the one-sentence description is insufficient. No output schema or return behavior details. Much more context is needed for correct invocation.

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 100% with detailed parameter descriptions. The tool description adds no extra meaning per parameter beyond the schema, so baseline of 3 is appropriate.

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?

Description clearly states the tool performs operations on Excel workbooks, listing read, write, and formulas. It is specific about the resource (Excel workbooks) and verbs (perform operations), but does not differentiate from sibling 'excel_analysis'.

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 'excel_analysis' or when not to use it. No exclusions or context provided.

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