Skip to main content
Glama

graph_list_drives

List all reachable Microsoft Graph drives, including OneDrive and followed document libraries, with paging support via skip or next_link.

Instructions

List the drives the user can reach, including their OneDrive and followed document libraries.

Args: skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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

Input Schema

NameRequiredDescriptionDefault
skipNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does meaningful work: it discloses the 50-item server-side cap, that next_link overrides other paging arguments, and that include_next_link controls whether results come back as {items, next_link} or a bare list. It stops short of stating auth requirements or ordering, but the paging and return-shape behavior are well covered.

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 purpose sentence is front-loaded and the Args block is compact, with every parameter note adding operational meaning rather than restating the schema. Slight verbosity in the repeated paging explanation ('page by raising skip in steps of top') keeps it from a top score.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, no-annotation, no-output-schema tool, the description covers the essentials an agent needs: scope of results, paging mechanics, override precedence, and return shape. Missing only secondary details such as result ordering or permission requirements.

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?

Schema description coverage is 0%, so the description must compensate and it does fully: skip is defined with its default and the step-size needed to page, next_link is described as an opaque URL that overrides other paging args, and include_next_link is explained with both its default and its effect on the returned structure.

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?

States a specific verb and resource ('List the drives') and scopes it with 'the user can reach, including their OneDrive and followed document libraries', which tells an agent what content to expect. It does not explicitly name or contrast with the sibling graph_list_site_drives, so differentiation is only partial.

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?

Usage is implied rather than stated: the paging instructions make clear this is a paginated enumeration call, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative tool (e.g. graph_list_site_drives or graph_list_files) is named as a routing option.

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