List all spreadsheets (sheets, excel, workbooks) with their tab metadata (no cell data). Use this when asked to list, find, or search spreadsheets, workbooks, tables, or tabular data.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort field | |
| limit | No | Max results (1-100, default 50) | |
| order | No | Sort order | |
| offset | No | Pagination offset | |
| server_id | No | Filter by server ID |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It adds useful behavioral context by noting that only tab metadata is returned and no cell data. However, it omits other behavioral traits such as pagination behavior or response format, leaving some gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, with the first sentence front-loading the core purpose and the second providing usage guidance. No unnecessary words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with 5 optional parameters and no output schema, the description covers the essential aspects: scope, exclusions, and usage. The full parameter documentation exists in the schema, so the description is sufficiently complete, with only minor missing details like pagination defaults.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, meaning all parameters are already well-documented in the schema. The description does not add extra parameter semantics beyond what the schema provides, 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('spreadsheets') with added scope ('with their tab metadata (no cell data)'). It clearly distinguishes from sibling tools like list_documents and list_slides by naming the target resource type.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool: 'Use this when asked to list, find, or search spreadsheets, workbooks, tables, or tabular data.' This provides clear usage context, though it does not explicitly mention exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool maps to a distinct resource and action: documents, sheets, slides, and servers. Even similar operations like update_sheet and update_sheet_tab are clearly separated by scope (workbook vs tab).
Most tools follow a verb_noun pattern (create_document, delete_sheet_tab, list_slides), but there are minor deviations: 'append_to_document' vs 'append_rows'/'append_slides', and 'create_slide_presentation' vs 'list_slides' use inconsistent naming lengths and pluralization.
With 23 tools, the server is slightly above the ideal 3–15 range but reasonable for covering three full document-type lifecycles (documents, spreadsheets, presentations) plus server listing. No tool feels redundant.
The server provides create, read, update, delete, list, and append operations for documents, sheets, and presentations, including tab-level management for spreadsheets. Minor gaps exist like no individual slide update or search across all resource types, but the core workflows are well-covered.