mcp-server-sharepoint

sp_drive_checkout_list

Read-onlyIdempotent

List files checked out from SharePoint. Includes original path, checkout time, and local working-copy path. Optionally verify server-side lock state.

Instructions

List the files this MCP profile currently has checked out (acquired via sp_drive_file_checkout). Returns each entry's original path, when checkout happened, and the local working-copy path. Read-only. With verify=True, additionally queries SharePoint to confirm the server-side lock state (server_locked + lock_holder fields); costs one Graph call per registry entry. Default verify=False is sub-second, registry-only — sp_drive_file_checkin's ETag round-trip catches divergence at write time.

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

Input Schema

Name	Required	Description	Default
`verify`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Jul 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral details: the default operation is sub-second registry-only, verify=True incurs Graph calls and adds server_locked/lock_holder fields, and that check-in handles divergence at write time. It fully discloses the behavior beyond annotations.

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?

The description is concise (3-4 sentences), front-loaded with the core purpose, and each sentence adds value without redundancy. It balances completeness with brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 optional param, no required params) and presence of an output schema, the description covers all necessary aspects: what it does, return values, performance trade-offs, and relationship to other tools (sp_drive_file_checkout, sp_drive_file_checkin). It is fully complete for an AI agent to use correctly.

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

Parameters5/5

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

The input schema has one optional boolean parameter 'verify' with default false and no description. The tool description fully explains its effect (triggers server-side lock check, adds fields, costs a Graph call), performance implications, and tie-in with check-in. This adds significant meaning beyond the schema schema.

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 'List the files this MCP profile currently has checked out' (verb+resource), mentions the origin (via sp_drive_file_checkout), and distinguishes from siblings by focusing on checked-out files. It also defines what is returned (original path, checkout time, local working-copy path).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: default verify=False is fast (registry-only), while verify=True queries SharePoint at a cost. It explains when to use each mode and references sp_drive_file_checkin's ETag mechanism, implying when not to use verify. This is clear, though it does not explicitly list alternative tools for other scenarios.

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