Skip to main content
Glama

sheet_schema

Lists every sheet with its folder and row count, or returns one sheet's columns, types, key, identity columns and filing instructions to guide structured data entry.

Instructions

Describe sheets. Called with no sheet, it lists every sheet with its folder and number of rows. Called with a sheet, it returns that sheet's columns, types, key, identity columns and filing instructions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sheet_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does well: it states exactly what is returned in each mode, including the schema-level details (types, key, identity columns, filing instructions) that an agent needs before querying. It stops short of confirming this is strictly read-only or noting whether results are paginated, but the wording ('lists', 'returns') makes the non-mutating nature evident.

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 tight sentences with no filler. The core capability leads, followed immediately by the parameter-driven branching, so an agent can extract the usage rule in one pass.

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 one-parameter, annotation-free, output-schema-free tool, the description covers both the invocation modes and the returned fields comprehensively. Only the identifier format and the meaning of the returned 'filing instructions' remain unexplained.

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

Parameters4/5

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

Schema coverage is 0%, so the description must define the single parameter, and it does: omitting sheet yields a catalog of all sheets, supplying it yields that sheet's structural metadata. The one gap is that it never says what form the identifier takes — sheet name versus internal ID — which could cause a failed call.

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?

The description uses a concrete verb and resource ('Describe sheets') and spells out two distinct modes: a metadata listing of every sheet with folder and row counts, or one sheet's columns, types, key, identity columns and filing instructions. It is clearly distinguished from the write operation implied by sheet_upsert, though it never explicitly contrasts itself with sheet_query, which reads data rather than describing structure.

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

Usage Guidelines3/5

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

The description explains how to select the two behaviors via the presence or absence of the sheet argument, which is useful operational guidance. However, it gives no explicit when-to-use versus sibling tools like sheet_query, and no exclusions or prerequisites are stated.

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