Skip to main content
Glama
Sign In
sharepoint-mcp

sharepoint-mcp

by ravikant1918
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delete_Folder

Delete empty folders from SharePoint by providing the full path to the folder.

Instructions

Delete an empty folder from SharePoint. Provide the full path to the folder to delete.

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": "Delete_Folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It reveals the destructive nature ('Delete'), but does not disclose error behavior for non-empty folders, permission requirements, or side effects. This lack of detail hinders safe usage.

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?

The description is brief (two sentences), and the first sentence clearly states the core purpose. However, it sacrifices essential detail for brevity, leaving out crucial constraints and usage context.

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 simplicity (1 parameter, no output schema), the description should fully cover behavior including error states and prerequisites. It does not address what happens if the folder is not empty, if the path is invalid, or if the user lacks permissions. This incompleteness may lead to invocation failures.

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?

The description adds minimal meaning to the single parameter 'folder_path' (schema has 0% description coverage). It says to 'Provide the full path' but does not specify format, example, or whether the parameter is required. Agents may struggle with correct invocation.

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 states 'Delete an empty folder from SharePoint', clearly indicating the action (delete) and the resource (empty folder). It distinguishes from sibling tools like Delete_Document which target documents. However, it omits a critical constraint: the folder must be empty, which could lead to misuse.

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 is provided on when to use this tool versus alternatives (e.g., Delete_Document) or what happens if conditions are not met (e.g., folder not empty). The instruction to 'Provide the full path' is minimal and does not help the agent decide when to invoke this tool.

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