Skip to main content
Glama

set_worksheet_title

Set or clear the visible plain-text worksheet title.

Instructions

Set or clear the visible plain-text worksheet title.

Input Schema

NameRequiredDescriptionDefault
titleYes
worksheet_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.28.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Set or clear' hints at clearing behavior but does not explain how clearing is triggered (empty string vs null), whether the change is persisted to the workbook, or what permissions are needed — significant gaps for a mutation tool.

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?

One front-loaded sentence with no filler. It is efficient, though the extreme brevity contributes to the missing details elsewhere rather than being a model of completeness.

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?

An output schema exists, so return values need not be explained. However, with no annotations, 0% parameter coverage, and an unexplained 'clear' mechanism, the definition leaves the agent without enough to invoke the tool correctly.

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 description coverage is 0% and neither parameter has a description, so the description must compensate and does not. It mentions 'title' conceptually but says nothing about how 'title' signals a clear, nor what 'worksheet_name' expects (internal name vs display name).

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 ('set or clear') and resource ('the visible plain-text worksheet title'), which is more precise than the generic siblings. It implicitly separates itself from set_worksheet_caption via 'plain-text title', but never names caption/hidden explicitly, so the sibling boundary is left to inference.

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?

No when-to-use guidance, no prerequisites, and no mention of the closely related siblings (set_worksheet_caption, set_worksheet_hidden). The agent must guess the context in which a worksheet title is set versus a caption.

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

Deploy Server

Other Tools