Skip to main content
Glama
Sign In
sharepoint-mcp

sharepoint-mcp

by ravikant1918
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get_SharePoint_Tree

Retrieve a recursive tree view of folders and files from any SharePoint directory. Specify a parent folder or use root to see the entire document library structure.

Instructions

Get a recursive tree view of folders and files starting from a SharePoint directory. Use None/null or empty string for document library root.

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_SharePoint_Tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
parent_folderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations present, so description must fully disclose behavior. It mentions recursion and tree view but omits details like depth limits, permission requirements, or performance implications.

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?

A single, well-structured sentence that immediately conveys the tool's purpose and key usage hint.

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?

Adequate for a simple tool with one parameter, but lacks information about return format, limitations, or comparison to sibling tools, which would improve completeness.

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?

With 0% schema description coverage, the description adds value by explaining how to specify the root directory (None/null/empty string), though the format of the parent_folder path is not elaborated.

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?

Clearly states it returns a recursive tree view of folders and files starting from a directory, distinguishing it from flat listing tools like List_SharePoint_Documents and List_SharePoint_Folders.

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?

Only provides guidance for the root parameter (use None/null/empty string) but does not specify when to use this tool versus siblings or mention any prerequisites.

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