Skip to main content
Glama

List SharePoint Document Libraries

list_site_drives
Read-only

List document libraries (drives) in a SharePoint site to identify available storage locations and choose the right library for file operations.

Instructions

List document libraries (drives) in a SharePoint site

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "list_site_drives"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesSite ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this is a non-mutating read, so the safety profile is covered. The description adds only the domain framing (site-scoped drives) and says nothing about result volume, pagination, or ordering; with annotations carrying the behavioral burden, this is adequate but thin.

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?

One short sentence with the verb and scope front-loaded and no redundant restatement of the title or schema. Nothing could be removed without losing meaning.

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?

For a simple single-parameter read tool with annotations covering safety and no output schema requirement, the definition is minimally sufficient. It is missing the one piece of workflow context an agent would benefit from: how to obtain a site_id and where to go next (list_drive_items) once drives are known.

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% for the single parameter, so the schema documents site_id itself. The description adds no format, source, or acquisition guidance for the site ID (e.g., obtainable via list_sites), so it neither compensates nor detracts; baseline 3 applies.

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 gives a specific verb (List) and resource (document libraries/drives) scoped to a SharePoint site, and the parenthetical maps the 'drives' terminology to 'document libraries', which disambiguates jargon. It does not, however, distinguish this from siblings such as list_drive_items or list_sites, so an agent must infer the boundary itself.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. The phrase 'in a SharePoint site' only implies that a site context is required, which the schema already enforces via required site_id.

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