Skip to main content
Glama

Coline

Protect a range

protect_sheet_range

Locks columns or rows of a table (or warns before edits), except for the people allowed. Only the sheet's owner can.

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>",
      "tableId": "<tableId>",
      "name": "<name>"
    },
    "name": "protect_sheet_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
nameYes
rowIdsNo
sheetIdYesSheet id from search, fetch or create_sheet.
tableIdYes
fieldIdsNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo
allowUserIdsNo

Output Schema

NameRequiredDescriptionDefault
protectionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare it is a non-readonly, non-destructive mutation, so the safety profile is partly covered. The description adds real value beyond them by disclosing the owner-only authorization requirement and the existence of a warn-before-edit mode. However, it does not explain reversibility, what happens if a protection already exists on the same range (relevant given idempotentHint=false), or how it interacts with existing protections.

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?

Two compact sentences with the action and the authorization constraint front-loaded; nothing is padded. Minor deductions for the telegraphic fragment 'Only the sheet's owner can.' and the informal phrasing 'the people allowed' instead of naming the allow-list concept.

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?

For a 9-parameter mutation tool with only 22% schema coverage, the definition is far too thin: it never clarifies that protection is scoped by tableId plus optional rowIds/fieldIds, nor how mode maps to readonly vs warning behavior. The presence of an output schema excuses it from describing return values, but the input-side gaps remain substantial.

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 only 22% (9 parameters, only sheetId and workspace documented), so the description must compensate and largely fails to. It loosely hints at allowUserIds ('except for the people allowed') and at the mode enum ('warns before edits'), but says nothing about rowIds, fieldIds, name, or description — the parameters that actually define which range gets locked.

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 conveys the core action (applying a lock to columns/rows of a table, with a warning variant) but uses vague framing rather than a precise verb+resource. It never distinguishes itself from the sibling tools update_sheet_protection, delete_sheet_protection, or list_sheet_protections, so an agent cannot tell whether this creates a new protection or modifies an existing one.

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 clause 'Only the sheet's owner can' gives a useful permission prerequisite, but there is no guidance on when to choose this tool over update_sheet_protection (existing protection) or list_sheet_protections (discovery). The agent is left to infer the create-vs-update boundary from the tool name 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