Skip to main content
Glama

graph_upload_file

Upload a small file (up to 4MB) to a specified OneDrive path using base64-encoded content through Microsoft Graph.

Instructions

Upload a small file to OneDrive (max 4MB).

Args: file_path: Destination path in OneDrive (e.g. "Documents/report.txt"). content_base64: File content encoded as base64 string.

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": {
      "file_path": "<file_path>",
      "content_base64": "<content_base64>"
    },
    "name": "graph_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
content_base64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It usefully states the 4MB maximum, but omits overwrite/replace semantics, required permissions or auth state, error behavior, and what the operation returns.

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?

The description front-loads the purpose and size limit, then compactly documents the two arguments. There is no redundant or filler text.

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 two-parameter write tool with no annotations and no output schema, the purpose and parameters are adequately covered. However, material context about overwrite behavior, permissions, and failure modes is missing, leaving real gaps for safe invocation.

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%, and the description compensates by defining both required parameters: file_path as an OneDrive destination with an example, and content_base64 as base64-encoded file content. This adds substantial meaning beyond the bare string types, though path constraints and overwrite implications remain unspecified.

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 ('Upload') and resource ('file to OneDrive'), with a clear 4MB size constraint. It does not explicitly name a sibling alternative for larger files, but the core purpose is unambiguous.

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 explicit when-to-use guidance versus alternatives, no prerequisites, and no exclusions beyond the implied 4MB limit. An agent can infer it is for small uploads but is not routed to another tool for larger files.

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