Skip to main content
Glama
rust-works

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

drive_sheets_read

Read cell values from a Google Sheets range, tab, or entire workbook. Choose formatted, raw, or formula output, and optionally write results to a YAML file.

Instructions

Read cell values from a spreadsheet: one A1 range/sheet, or — when both are omitted — every sheet in the workbook (capped at 200 sheets; narrow with sheet/range above that cap, rather than returning a partial workbook). render controls how values come back: formatted (default) matches the spreadsheet as displayed, unformatted gives raw typed numbers/booleans, formula gives formula text. Values are returned ragged exactly as the API returns them (trailing empty cells/rows truncated). When output_file is set, writes the YAML result to that path and returns a short summary instead — recommended for a large whole-workbook read. Read-only — no write gate or dry-run applies (unlike sheets write/append/clear, whose MCP handlers live in drive_write_tools). Mirrors omni-dev drive sheets read. Output is YAML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeNoAn explicit A1 range, which may carry its own `Sheet!` prefix (e.g. `A1:C10`, `'My Sheet'!A:A`). Combined with `sheet` when bare. Omit both `range` and `sheet` to read every sheet in the workbook (capped at 200 sheets; narrow with `sheet`/`range` above that cap).
sheetNoSheet (tab) title to read. Supplies the prefix for a bare `range`, or selects the whole tab on its own. Conflicts with a `range` that already names a sheet.
renderNoHow cell values are rendered. `formatted` (default) matches the spreadsheet as displayed; `unformatted` yields raw typed numbers rather than locale-formatted strings; `formula` yields formula text.
accountNoSelects a named Drive account instead of the ambient `--account`/`OMNI_DEV_DRIVE_ACCOUNT` resolution — e.g. `work`. Omit to use the resolved default account (or the legacy single-account credentials, if no named accounts are configured). Call `drive_account_list` to discover configured names.
output_fileNoWhen set, writes the result (YAML) to this path and returns a short summary instead of the inline body — recommended for a whole-workbook read that would exceed the response size limit.
spreadsheet_idYesSpreadsheet id (the `/d/<ID>/` segment of a Sheets URL). Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.44.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so richly: read-only, no write gate/dry-run, ragged values with trailing empty cells/rows truncated, render-mode semantics, the 200-sheet cap, output_file side effect, and YAML output format are all 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?

Front-loads the core action (read cell values) then layers scope, render, output behavior. Dense but each sentence is informative. Slightly heavy, with a few clauses that could be tightened, but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description explains the return format (YAML), ragged value behavior, and the output_file summary alternative. Combined with full schema coverage and six parameters, an agent has everything needed to invoke it correctly.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description largely restates schema content (render modes, range/sheet combination, output_file). It adds marginal value by explaining the range+sheet interaction and the whole-workbook default, but the schema already documents these, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read cell values from a spreadsheet') with scope detail (single range/sheet vs whole workbook). It also distinguishes itself from siblings by naming the write operations (`sheets write`/`append`/`clear`) it is not, so an agent can separate it from drive_sheets_write/append/clear without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to omit both `range` and `sheet` (whole workbook), the 200-sheet cap and how to narrow above it, when to use `output_file` (large whole-workbook read), and contrasts with write tools. Alternatives and conditions are all named.

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