Skip to main content
Glama

sheets_discover

Read-only

Discover available Google Sheets operations. Call this first to list and filter capabilities, then invoke the desired operation by name.

Instructions

List the available sheets operations. Operational sheets tools are hidden until discovered — call this first, then call the tool you need by name. Operations: create, get, read_range, write_range, append_rows, clear_range, batch_read, batch_write, add_sheet, delete_sheet, duplicate_sheet, update_sheet_properties, format_cells, update_borders, merge_cells, unmerge_cells, add_conditional_format_rule, sort_range, set_basic_filter, clear_basic_filter, find_replace, auto_resize_dimensions, insert_dimension, delete_dimension, set_data_validation, add_named_range, delete_named_range, batch_clear, batch_update, spreadsheets_developer_metadata_get, spreadsheets_developer_metadata_search, spreadsheets_get_by_data_filter, spreadsheets_sheets_copy_to, spreadsheets_values_batch_clear_by_data_filter, spreadsheets_values_batch_get_by_data_filter, spreadsheets_values_batch_update_by_data_filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoKeyword to filter the returned operations
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the discovery mechanism (hidden until called), which is useful behavioral context beyond the annotations.

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 description is front-loaded with the core purpose and usage instruction, followed by a comprehensive operation list. While the list is long, it is necessary for a discovery tool and each entry is relevant.

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?

For a low-complexity discovery tool with no output schema, the description fully explains the tool's behavior and enumerates all discoverable operations. No additional context is needed.

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?

The schema fully describes the single optional 'query' parameter (100% coverage), and the tool description does not mention it. With high schema coverage, a 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?

The description clearly states 'List the available sheets operations' with a specific verb and resource. It distinguishes itself from sibling discovery tools by being sheets-specific and by indicating it reveals hidden operational tools.

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 instructs to 'call this first' and then call the needed tool by name, with the rationale that operational tools are hidden until discovered. This provides clear when-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bakissation/mcp-google-multi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server