Skip to main content
Glama

graph_restore_file_version

Restores a file to an earlier version using its file ID and version ID, optionally targeting a specific drive or your own OneDrive.

Instructions

Restore a file to an earlier version.

Args: item_id: The file ID. version_id: The version ID (from graph_list_file_versions). drive_id: Drive ID to act on. Empty targets your own OneDrive.

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>",
      "version_id": "<version_id>"
    },
    "name": "graph_restore_file_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
drive_idNo
version_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it does not say that this is a state-changing write, whether it overwrites the current file, whether the current version is preserved in version history, or what permissions are required. Only the drive_id default behavior 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose statement is front-loaded in one sentence and the Args block is compact, with every line adding parameter meaning. The 'Args:' formatting is serviceable rather than polished, and the version_id note could be slightly tighter.

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 three-parameter mutation with no output schema, the description covers all inputs but leaves the post-restore outcome and permission requirements unstated. Given zero annotation coverage on a write operation, a fuller behavioral note would raise it.

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%, but the description compensates by naming all three parameters, sourcing version_id from graph_list_file_versions, and explaining that an empty drive_id targets the caller's own OneDrive. It falls short of 5 only because it does not clarify item_id scope (which drive/user's file) or ID format.

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 states a concrete verb and resource ('Restore a file to an earlier version') that is unambiguous and clearly distinct from list/copy/delete/file-content siblings. It even points to graph_list_file_versions as the source of a required ID, aiding routing, though it does not explicitly contrast with other restore/overwrite paths.

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 by the restore semantics, and the description tells where version_id comes from, but there is no explicit when-to-use/when-not framing (e.g., restore vs. re-upload or copy). It also omits prerequisites such as having versioning enabled or write permission on the drive.

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