Skip to main content
Glama

graph_update_worksheet_range

Writes cell values into a specified Excel worksheet range using a 2D array whose shape matches the target address, enabling updates to .xlsx workbooks through Microsoft Graph.

Instructions

Write cell values to a worksheet range.

Excel workbook APIs need the Files.ReadWrite permission and only work on .xlsx files.

Args: item_id: The workbook file ID. worksheet: Worksheet ID or name. address: Range address to write (e.g. "A1:D10"). Its shape must match values. values: Cell values as a 2D array, one inner array per row. Cells may be strings, numbers, booleans, or null. 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>",
      "worksheet": "<worksheet>",
      "address": "<address>",
      "values": "<values>"
    },
    "name": "graph_update_worksheet_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes
addressYes
item_idYes
drive_idNo
worksheetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does cover the important parts: this is a write/mutation, it needs Files.ReadWrite, and it is limited to .xlsx files. It does not say whether existing cell contents in the target range are overwritten, what happens if the range and values shapes mismatch, or what the call returns on success or failure.

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 short lead sentence front-loads the purpose, then a compact Args block where each line carries a constraint rather than restating the parameter name. Slightly boilerplate in its docstring formatting, but no sentence is wasted.

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 five-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition covers auth, file-type limits, and parameter meaning reasonably well. It still leaves out overwrite semantics and return/error behavior, which an agent needs before performing a destructive-looking write.

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 do all the work, and it documents all five parameters. It adds real meaning beyond the bare schema: address shape must match values, values is a 2D row-major array with permitted cell types, and an empty drive_id targets your own OneDrive. Missing only finer detail such as accepted worksheet name vs. ID formats.

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: 'Write cell values to a worksheet range.' That is unambiguous and distinguishable from the read counterpart graph_get_worksheet_range by the verb alone. However, the description never names or contrasts with that read sibling, so the differentiation is implicit rather than stated.

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?

It supplies real preconditions: the Excel workbook APIs require Files.ReadWrite permission and only work on .xlsx files. That tells an agent when the call can succeed but gives no guidance on when to prefer another tool (e.g., the read variant) or when not to use this one.

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