Skip to main content
Glama

看电子表格有哪些工作表

feishu_sheet_meta
Read-only

Retrieves worksheet metadata from a Feishu spreadsheet, returning each sheet's sheet_id, title, and row/column counts so you can target write operations correctly.

Instructions

列出表格里每个工作表的 sheet_id、标题、行列数。写值前先看这个:飞书的写入接口要 sheet_id,而表格链接里给的是 spreadsheet_token,两者不是一回事。feishu_sheet_write 不带 sheet 前缀时会自动取第一个工作表,所以简单场景可以跳过这一步。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "spreadsheet_token": "<spreadsheet_token>"
    },
    "name": "feishu_sheet_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
spreadsheet_tokenYes电子表格 token(链接里 /sheets/ 后面那串)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the token-vs-sheet_id mismatch that motivates the call, and the fact that feishu_sheet_write silently defaults to the first worksheet. It omits pagination or rate-limit behavior, but for a small metadata read that is a minor gap.

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?

Three short sentences, front-loaded with what is returned, then the reason to call it, then the reason it can be skipped. No redundant restatement of the tool name or title, and every sentence carries decision-relevant information.

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?

With one required parameter, full schema coverage, and no output schema, the description closes the remaining gap by naming the return fields itself. An agent has everything needed to decide whether to call it and what it will get back.

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 100% and the single parameter is already documented as the token after /sheets/ in the link, so the baseline is 3. The description earns an extra point by explicitly warning that spreadsheet_token is not the sheet_id the write API expects — a conceptual distinction the schema alone does not make.

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?

States a specific verb and resource — lists every worksheet in a spreadsheet — and enumerates the returned fields (sheet_id, title, row/column counts). This distinguishes it cleanly from feishu_sheet_read and feishu_sheet_write without the agent needing to open any schema.

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?

Gives an explicit when-to-use rule (before writing values, because the write API needs sheet_id while links only carry spreadsheet_token) and an explicit when-to-skip rule (feishu_sheet_write without a sheet prefix auto-selects the first worksheet). Both the condition and the named alternative are present.

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