Skip to main content
Glama

Google_sheets

by io.github.pipeworx-io

Sheets Get Spreadsheet

sheets_get_spreadsheet
Read-onlyIdempotent

Explore a spreadsheet's structure. Returns title, sheet/tab names, and properties. Use before reading or writing data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_idYesSpreadsheet ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection required
sheetsNoList of sheets/tabs in the spreadsheet
messageNoError message if connection required
propertiesNoSpreadsheet properties
spreadsheetIdNoSpreadsheet ID

TDQS

A4/5.0
Behavior3/5

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

Annotations already specify readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds that it returns title, sheet/tab names, and properties, which is consistent but does not introduce new behavioral traits beyond what annotations imply.

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?

Two concise sentences: first states function, second gives usage advice. No redundant or unnecessary information, each sentence earns its place.

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?

The tool is simple with one parameter and an output schema (not shown). Description mentions key return items (title, names, properties), which is sufficient. Could be slightly more specific about 'properties,' but overall complete given context.

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 only parameter 'spreadsheet_id' is described as 'Spreadsheet ID' with an example. The description does not add additional meaning or formatting requirements beyond the schema.

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?

Description explicitly states the tool explores spreadsheet structure and lists return items (title, sheet/tab names, properties). It also suggests a use case before reading/writing, clearly distinguishing it from sibling tools like sheets_read, sheets_write, sheets_append.

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

Usage Guidelines4/5

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

Description explicitly states 'Use before reading or writing data,' providing clear context for when to use. While it does not mention alternatives, the usage guidance is direct and helpful.

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

All Google_sheets toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Several tools are nearly identical: ask_pipeworx and ask_pipeworx_beta are explicitly the same, and ask_pipeworx, ask_pipeworx_grounded, and deep_research all serve overlapping research/query purposes. discover_tools and suggest_questions both act as discovery entry points, while the five polymarket tools differentiate primarily through intricate details that are easy to confuse.

Naming Consistency2/5

Naming conventions are mixed across the set: verb_noun (ask_pipeworx, resolve_entity, validate_claim), noun_verb (sheets_append, sheets_create), noun_noun (polymarket_arbitrage, entity_profile), and bare verbs (forget, recall, subscribe). The sheets tools are internally consistent but the broader collection has no uniform pattern, with awkward names like pipeworx_trending and search_within.

Tool Count2/5

With 36 tools, the server exceeds the 25-tool threshold for 'too many'. The Google Sheets portion accounts for only 5 tools, while the majority are highly specialized Pipeworx and Polymarket tools that could be consolidated or dramatically reduced. The count feels inflated relative to the advertised 'Google_sheets' server name and its actual core purpose.

Completeness2/5

For a server named Google_sheets, the essential operations exist (create, read, write, append, list structure), but there is no delete/clear range tool and no way to add a new sheet to an existing spreadsheet. For the broader data/research scope, important lifecycles are missing (e.g., no direct way to write Pipeworx results into Sheets, no update for subscriptions, only cancel). The set falls short of fully covering either domain.

Resources