Skip to main content
Glama

Coline

Unprotect a range

delete_sheet_protection
DestructiveIdempotent

Removes a protected range.

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>",
      "protectionId": "<protectionId>"
    },
    "name": "delete_sheet_protection"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that — no statement of whether the removal is recoverable, what happens to the protected users, or that the protectionId must come from a listing call. For a destructive, non-recoverable-sounding operation this is a thin disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero filler, which is structurally clean. However, the brevity is under-specification rather than conciseness for a destructive tool with three required parameters.

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, so return values need not be explained, and the annotations carry the destructiveness signal. Still, for a mutation tool whose protectionId is undocumented and whose target (sheet vs. range) is inconsistent with the name, the description should do more to make the call unambiguous.

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%, with protectionId carrying no description at all, and the description does not compensate by explaining that protectionId is the identifier of the protection to remove or where to obtain it. The workspace and sheetId semantics are documented in the schema, so only the undocumented parameter matters, and the description is silent on it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and resource ("Removes a protected range"), but the resource it names ("range") does not match the tool name (delete_sheet_protection) nor the required sheetId parameter. An agent can guess the intent, yet the sheet-versus-range framing leaves a real ambiguity about what object is actually being unprotected.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as update_sheet_protection for modifying protection or list_sheet_protections for discovering the protectionId. The agent must infer the entire workflow from sibling names alone.

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