Skip to main content
Glama

onedrive_shared

Read-only

List files and folders others shared with you in OneDrive and return drive IDs for reading their contents.

Instructions

List files and folders other people shared with me. Read them with onedrive_read and the drive_id shown.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the non-obvious operational fact that the result carries a drive_id that must be handed to onedrive_read. It does not mention pagination or result caps, which matters for an open-world listing, but the core cross-tool workflow is disclosed.

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?

Two short sentences with zero filler; the identifying scope comes first and the follow-up action second. Every clause earns its place.

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 zero-parameter read tool with an output schema, annotations, and a named follow-up tool, the description supplies everything needed to invoke it correctly. Only the scale of results (a shared-with-me listing can be large and open-world) is unaddressed.

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?

The tool takes no parameters, so there is no parameter meaning to add and the description correctly spends its words elsewhere. Nothing in the schema is left ambiguous by the description.

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?

States a specific verb (List) and a scoped resource (files and folders other people shared with me), which immediately separates it from onedrive_list, onedrive_search, and the other drive tools. An agent can pick this without opening any schema.

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 phrase 'other people shared with me' implies when to choose this over listing a personal drive, and the second sentence routes the agent onward to onedrive_read. It stops short of naming a concrete exclusion (e.g. 'use onedrive_search to find your own files'), so guidance is clear but not exhaustive.

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