Skip to main content
Glama

Edit sheet (structured)

edit_sheet

Apply typed operations to a wiki sheet: set cells, insert or delete rows/columns, change styles, and freeze panes, all atomically in single or batch edits.

Instructions

Make a STRUCTURED edit to a sheet (a sheet=true page), editor+. Prefer this over update_page for sheets: you pass a typed operation and tela rewrites the Defter markdown correctly — inserting a row shifts every formula below it, deleting a column re-references the rest, so you never corrupt the grid by hand-editing text. Pass one op (or a batch via ops, applied atomically). Each op is {kind, ...} where kind is one of: setCells {cells:[{ref:"B2",text:"=A2*1.2"}]} — write literals/formulas by A1 ref; insertRows/deleteRows {at:<1-based row>, count?}; insertCols/deleteCols {at:<col letter or 1-based index>, count?}; setStyle {target:"A1:C1"|"B"|"2", attrs:{...}} — bold/align/fill/number-format a range/col/row; setFreeze {rows?, cols?} — freeze N header rows / M leading cols (0 clears); addSheet {name, after?}; renameSheet {sheet, name}; deleteSheet {sheet}. Ops that target a specific tab take an optional sheet (name or 0-based index; defaults to the first). A bad ref/range/sheet is rejected with a fixable error. Call sheet_authoring_guide for the full op reference, cell/style syntax, and formula functions. Returns the updated sheet with formulas computed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opNoa single SheetOp object with a 'kind' field. Provide this OR ops.
opsNoan ordered batch of SheetOps applied atomically (all-or-nothing; the sheet is only rewritten if every op succeeds). Provide this OR op.
page_idYesthe sheet page id to edit (a page with sheet=true)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
Behavior5/5

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

Annotations only state non-read-only. The description adds critical behavioral details: operations are atomic, errors are fixable, returns updated sheet with computed formulas, and warns against manual editing to avoid grid corruption. This far exceeds the annotation burden.

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 dense but well-structured, starting with purpose and preference. Every sentence adds value, though it is slightly verbose for a single tool. Could be tightened by removing redundant 'Pass one op (or a batch...)', but overall efficient.

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?

Given the tool's complexity (multiple op kinds, batch, atomicity, output schema), the description is remarkably complete. It covers all key aspects: permission, behavior, error handling, output, and points to additional reference. No significant gaps remain.

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

Parameters5/5

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

Schema coverage is 100%, yet description adds substantial meaning: explains 'op' structure with examples per kind, 'ops' batch with atomicity, and clarifies 'page_id'. Provides context that schema alone cannot, like 'A1 ref' and optional 'sheet' per op.

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 the verb 'edit' and resource 'sheet', differentiates from 'update_page' by explicitly preferring this tool for sheets, and specifies 'STRUCTURED edit' with 'editor+' permission. It leaves no ambiguity about what the tool does and its unique value.

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?

The description explicitly advises 'Prefer this over update_page for sheets', implying when to use (sheets) and when not (non-sheet pages). It also directs to 'sheet_authoring_guide' for full details, providing clear guidance on alternatives and additional resources.

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/zcag/tela'

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