Skip to main content
Glama

graph_get_worksheet_range

Read cell values from a worksheet range in an Excel workbook, returning rows of values for a specified address or the used range when no address is given.

Instructions

Read cell values from a worksheet range.

The response values array holds the cell values, one inner array per row. 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 (e.g. "A1:D10"). Empty reads the used range. 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>"
    },
    "name": "graph_get_worksheet_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNo
item_idYes
drive_idNo
worksheetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose useful traits: the required Files.ReadWrite permission, that only .xlsx workbooks are supported, and the shape of the returned `values` array (one inner array per row). It does not cover failure modes for non-.xlsx files, empty-cell representation (null vs empty string), or what happens when the address exceeds the used range.

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?

Front-loaded purpose sentence, then return shape, then environment constraints, then a clean Args block. Every line carries information, though the split between the prose sections and the Args block is slightly redundant in framing.

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?

For a four-parameter read tool with no output schema and no annotations, the definition covers the essentials: purpose, return shape, auth/file-type constraints, and per-parameter meaning. Gaps remain around null handling for blank cells and out-of-range addresses, which are the likely runtime surprises, but the core is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 compensate, and it documents all four parameters: item_id as the workbook file ID, worksheet as ID or name, address with a concrete format example plus the empty-string behavior ('Empty reads the used range'), and drive_id with the default ('Empty targets your own OneDrive'). This adds real meaning the bare schema lacks, including default semantics.

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 opening line names a specific verb and resource ('Read cell values from a worksheet range'), which cleanly separates it from the read/write split implied by the sibling graph_update_worksheet_range. It is clear but never names or contrasts an alternative directly, so it stops just short of full sibling differentiation.

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?

The description gives a precondition ('only work on .xlsx files', Files.ReadWrite requirement) but no when-to-use/when-not-to-use guidance or routing to alternatives such as a general file-content read. The agent is left to infer when this range reader is the right choice over other file tools.

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