Skip to main content
Glama

Coline

Create a sheet

create_sheet

Creates a sheet (a tracker, list or table) with typed columns and optional rows, shown to the person as it fills. Rows are cell values keyed by column name.

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": {
      "workspace": "<workspace>"
    },
    "name": "create_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNo
titleNoDefault: Untitled sheet.
columnsNoThe table's columns; without them the sheet starts from a template (blank by default).
driveIdNoDefault: the person's own drive.
parentIdNoA folder in that drive.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
templateKeyNoA starting template, when no columns are given.

Output Schema

NameRequiredDescriptionDefault
urlYes
sheetIdYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds one piece of genuine behavioral context, that the sheet is "shown to the person as it fills" (a live, user-visible effect), but says nothing about permissions, whether repeated calls create duplicates, or limits.

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?

A single front-loaded sentence with no filler; the parenthetical and the final clause are short and each does work by disambiguating "sheet" and clarifying row structure.

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 and the input schema is richly documented, so return values and parameter details need not be restated. Still missing is the interaction between columns and templateKey and the fact that workspace is required, gaps an agent must resolve by reading the schema.

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

Parameters3/5

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

Schema description coverage is 86%, so the schema already explains columns, templateKey, driveId, parentId and workspace. The description's note that "rows are cell values keyed by column name" restates the schema's own wording and adds no format, ordering, or type-coercion guidance.

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 gives a specific verb and resource ("Creates a sheet") and disambiguates the term with a parenthetical ("a tracker, list or table") plus the notion of typed columns and optional rows. It is clear what the tool produces, though it never contrasts itself with nearby tools like add_sheet_columns or create_sheet_automation.

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?

Usage is only implied: an agent can infer this is the creation entry point versus column/automation tools, but there is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g. that a workspace slug is mandatory). The only conditional behavior, template fallback, is stated in the schema rather than the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources