Skip to main content
Glama

onedrive_read

Read-only

Read a OneDrive file as text by item ID or path, and include drive_id for shared files, to extract document contents.

Instructions

Read a OneDrive file as text. Give item_id (from a listing or search) or path (e.g. /Documents/notes.docx). For a file shared with you, also give its drive_id.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
item_idNo
drive_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external reach are covered. The description usefully adds that output is text rather than raw bytes, but says nothing about size limits, pagination/truncation, or what happens with unsupported or binary formats — meaningful gaps for a read tool whose value depends on content fidelity.

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?

Three short sentences, front-loaded with purpose, then identifier options, then the conditional third parameter. No filler or restatement of the title.

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?

An output schema exists, so return-value explanation is not required, and the description covers the identifier strategy that is otherwise undocumented. The remaining omission is conflict behavior between item_id and path and any file-type or size constraints.

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?

Schema description coverage is 0%, so the description must carry the load, and it does: it names all three parameters, gives a concrete path example ("/Documents/notes.docx"), and explains drive_id's purpose (files shared with the caller). It does not say what happens if both item_id and path are supplied or which takes precedence.

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 and resource ("Read a OneDrive file as text") and the text-conversion aspect distinguishes it from onedrive_list, onedrive_search, and onedrive_shared, which locate files rather than return content.

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?

Implies the workflow — identifiers come "from a listing or search" — and tells the agent to add drive_id only "for a file shared with you," which is a real conditional. No explicit exclusion for non-text or binary files, so just short of a 5.

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