Skip to main content
Glama

list_tabs

Lists tab names in a shared Google Sheet so AI agents can identify the correct issue worksheet before reading open items or appending replies.

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": "list_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/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 discloses essentially nothing: not whether hidden or protected tabs are included, not the ordering, not whether it requires auth or a sheet context. It only restates the resource being enumerated, leaving behavior entirely to inference.

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?

It is a single short sentence with no filler, which is appropriate for a trivial tool, but the terseness crosses into under-specification rather than economy. Nothing is front-loaded because nothing is elaborated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and with zero parameters the surface area is small. Still, the definition omits any statement of scope (all tabs? visible tabs?) that an agent would want before relying on the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. Baseline 4 applies; a sentence noting how the sheet is identified implicitly (via session/context) would have earned a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "시트의 탭 이름 목록" (list of tab names in the sheet) identifies a specific resource — tab names of a spreadsheet — but is a bare noun phrase with no verb, so it reads more like a label than a description. It is distinguishable from siblings such as read_tab or list_issues by resource, but the definition itself does nothing to draw that contrast.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of how this differs from read_tab (which presumably returns tab contents), and no stated preconditions such as needing a spreadsheet identifier. The agent must infer everything from the name alone.

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