Skip to main content
Glama
bakissation

mcp-google-multi

by bakissation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sheets_discover

Read-onlyIdempotent

Lists available Google Sheets operations and hidden tools so you can call the right action by name; run this first to explore create, read, write, and sheet management options.

Instructions

Discover sheets: lists the catalog and reveals its hidden tools; call first, then call the tool by name. Ops: create, get, read_range, write_range, append_rows, clear_range, batch_read, batch_write, add_sheet, delete_sheet +19 more; 7 generated ops: spreadsheets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFilter keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.4.1
    • changedInput schema / properties / query / description
      Previous value: -"Keyword to filter the returned operations"New value: +"Filter keyword"
  2. First observedv0.0.0-semantically-released

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, so the safety bar is low. The description adds genuinely useful behavior beyond that: this tool reveals hidden tools and must be called before the real operation, which is non-obvious discovery semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and earns its place, but the semicolon-delimited op enumeration trails off with '+19 more; 7 generated ops: spreadsheets', which is cryptic and partially incomplete noise rather than actionable content.

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 single-param, read-only discovery tool with no output schema, the description covers what it returns (a catalog), how to use it (call first), and what it unlocks. The truncated op list is the only rough edge.

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?

One optional parameter with 100% schema description coverage ('Filter keyword'), so the schema already carries the semantics. The description adds nothing about how the query filter works, so baseline 3 is correct.

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 ('Discover sheets: lists the catalog and reveals its hidden tools') and its scope is clear versus sibling discovery tools by naming the domain. It doesn't explicitly differentiate itself from discover_all, which is the nearest alternative.

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?

'call first, then call the tool by name' gives explicit sequencing guidance for how this tool fits into a workflow. It stops short of stating when NOT to use it or how it differs from discover_all/discover_reset.

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