sharepoint-mcp

Get_Document_Content

Retrieve and decode content from SharePoint PDF, Word, Excel, or plain-text files. Use folder_name or leave empty for documents in the library root.

Instructions

Retrieve and decode the content of a SharePoint document. Supports PDF, Word, Excel, and plain-text files. For files in the document library root, use empty string for folder_name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "Get_Document_Content"
  }
}

Input Schema

Name	Required	Description	Default
`folder_name`	No
`file_name`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, so description must fully convey behavioral traits. It mentions decoding and supported formats but omits critical details like return format (text vs binary), authentication requirements, or file size limits. Minimal transparency beyond basic function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words. First sentence captures primary action, second provides a specific usage hint. Excellent front-loading and brevity.

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?

Despite existence of output schema, the description fails to clarify parameter usage and tool differentiation. Given two undefined parameters and no annotations, the description is too sparse to be complete. Sibling tools require clearer distinction.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description must add meaning. It partially explains folder_name (use empty for root) but gives no guidance on file_name parameter, its format, or how the two interact. Incomplete semantic coverage.

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 retrieving and decoding SharePoint document content and lists supported file types. However, it does not explicitly differentiate from sibling tools like Download_Document or Get_File_Metadata, which might overlap in purpose.

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?

Provides a specific hint about using empty string for folder_name when file is in root, but lacks any guidance on when to use this tool versus alternative sibling tools. No when-not-to-use or prerequisite conditions mentioned.

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

Deploy Server