Skip to main content
Glama

sheets read range

sheets_read_range
Read-onlyIdempotent

Read a specific A1 range from a Google Sheet to retrieve cell values for analysis or reporting. Read-only access supports scoped agent workflows without modifying spreadsheet data.

Instructions

Read an A1 range (e.g. 'Sheet1!A1:D20') from a spreadsheet. Read-only.

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "range_a1": "<range_a1>"
    },
    "name": "sheets_read_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
range_a1Yes
value_renderNoFORMATTED_VALUE
spreadsheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description's only behavioral statement, 'Read-only,' simply repeats the readOnlyHint annotation and adds no further context such as error behavior or range-not-found handling.

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 definition is short and front-loaded: the core operation comes first, followed by an A1 example and a safety note. The final 'Read-only' clause is redundant with the annotations, but the overall structure is efficient and easy to parse.

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, and because an output schema exists the description needn't explain return values. However, for a three-parameter read tool with 0% schema coverage, the description should at least mention value_render and ideally route batch reads to sheets_batch_read, so it is only minimally complete.

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

Parameters2/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 carry parameter meaning. It clarifies the range_a1 format with an example ('Sheet1!A1:D20') but says nothing about value_render, which defaults to FORMATTED_VALUE and has materially different modes, nor does it explain spreadsheet_id. Only one of three parameters is meaningfully documented.

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 specific verb and resource ('Read an A1 range ... from a spreadsheet') and includes a concrete range example, so the agent knows exactly what operation this performs. It does not explicitly differentiate itself from siblings such as sheets_batch_read, which prevents a top score.

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 or when-not-to-use guidance. The purpose implies a single-range read, but the description never states that sheets_batch_read should be used for multiple ranges or that sheets_update_range is the write counterpart, leaving the agent to infer alternatives from names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.