Skip to main content
Glama

Get OneDrive File Details

get_drive_item
Read-only

Retrieve metadata for a file or folder in OneDrive or SharePoint by its drive item ID, so an AI assistant can inspect names, sizes, and details before acting on it.

Instructions

Get file or folder metadata

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": {
      "item_id": "<item_id>"
    },
    "name": "get_drive_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesDrive item ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's remaining obligation is to add context — and it adds none. It doesn't say which metadata fields come back, whether permissions or errors differ for folders vs files, or how authentication affects results.

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?

A single front-loaded phrase with zero filler, which is the right shape for a trivial one-parameter read. It is efficient but so terse that brevity shades into under-specification.

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?

The tool is simple — one required ID, no nesting, annotations covering safety — so not much is needed. However, with no output schema the agent has no idea what 'metadata' contains, and the description does not fill that gap.

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?

With a single parameter at 100% schema coverage, the schema already documents item_id, so baseline 3 applies. The description adds no format hints for a drive item ID (e.g. the encoded '01ABCD...' style) or whether a path is acceptable, so it contributes no meaning beyond the schema.

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 ('Get file or folder metadata'), which is enough to contrast with the sibling list_drive_items by singularity of the target. It does not explicitly name any sibling or say how it differs from e.g. download_file, so it stops short of a 5.

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 when-to-use guidance at all: nothing says to call this before download_file/upload_file, or that it is the way to resolve an item_id before a mutation. The agent must infer the call context purely from the tool name.

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