Skip to main content
Glama

Coline

Rename a sheet

rename_sheet
Idempotent

Renames a sheet the person can edit.

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>",
      "sheetId": "<sheetId>",
      "title": "<title>"
    },
    "name": "rename_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
sheetIdYesSheet id from search, fetch or create_sheet.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and repeat-call profile is covered. The description adds only the edit-permission precondition; it says nothing about name-collision behavior, invalid characters, or what the response contains.

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?

A single short sentence with zero filler, front-loaded with the verb. It is efficient, though the brevity buys conciseness at the cost of the missing details noted above.

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

Completeness2/5

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

With three required parameters, an output schema and a mutation annotation set, the description should at least confirm the naming contract and the permission requirement in more detail. It leaves the title parameter, collision handling and result shape entirely to the structured fields, which only partially cover them.

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

Parameters2/5

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

Schema coverage is 67%: sheetId and workspace already carry descriptions, while title only has length bounds. The description never mentions the title argument or any naming rules, so it adds no meaning beyond the schema for the one parameter that is weakest documented.

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?

States a specific verb and resource ("Renames a sheet") and adds a permission qualifier ("the person can edit"), so the action is unambiguous. It does not distinguish itself from siblings like rename_drive, but the verb+resource pair is clear enough on its own.

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?

The phrase "the person can edit" implies an edit-permission prerequisite, which is useful, but there is no guidance on when to pick this tool versus alternatives such as create_sheet or rename_drive, nor any statement about what to do when the target name already exists.

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