Skip to main content
Glama

Coline

Remove a sheet role

remove_sheet_role
DestructiveIdempotent

Removes a role from a sheet, so Drive access applies again.

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>",
      "grantId": "<grantId>"
    },
    "name": "remove_sheet_role"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds one useful behavioral fact beyond that: the effect on access, namely that Drive permissions apply again after removal. It does not say whether removal requires specific permissions, what happens if the grant does not exist, or whether the change is reversible.

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 no filler, and the core action is front-loaded. It is terse to the point that it omits the identifiers involved, but nothing written is wasted.

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 no explanation, and the three required parameters are at least partly documented in the schema. Still, for a destructive mutation, the description fails to say how to obtain grantId or what prerequisites govern the call, leaving gaps that the annotations and schema do not fill.

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 67%: sheetId and workspace are documented in the schema, but grantId has no description anywhere. The description does not mention grantId or explain how to obtain it (presumably from get_sheet_roles), so it adds no parameter meaning beyond the schema and leaves the single undocumented parameter unexplained.

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 the specific verb and resource ('Removes a role from a sheet'), which clearly separates it from set_sheet_role and get_sheet_roles. It does not name those siblings explicitly, but the action direction (remove vs set/get) is unambiguous.

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?

The clause 'so Drive access applies again' implies the scenario in which this tool is the right one (clearing a sheet-level role so Drive permissions take over), but there is no explicit when-to-use or when-not-to-use guidance and no mention of the alternative set_sheet_role for changing rather than removing a role.

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