Skip to main content
Glama

Coline

Set a sheet role

set_sheet_role
Idempotent

Sets someone's role on a sheet, or everyone's in the workspace. 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>",
      "subjectType": "<subjectType>",
      "role": "<role>"
    },
    "name": "set_sheet_role"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
grantYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover idempotency, non-destructiveness, and write semantics, so the bar is lower; the description's contribution is the owner-only authorization constraint, which is genuinely useful context not captured in structured fields. It omits other notable behavior, such as what happens to the prior holder when role is set to 'owner' or whether an existing role is overwritten.

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 operation stated first and the permission constraint second; no filler. The fragment 'Only the sheet's owner can.' is terse but still readable.

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

Completeness5/5

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

With an output schema present, return values need not be described, and annotations already carry the safety profile. For a five-parameter mutation, the remaining essentials are the operation, its scope, and the authorization gate, all of which are stated.

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

Parameters3/5

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

Schema coverage is only 40%; workspace and sheetId are described in the schema, but subjectUserId has no description anywhere. The phrase 'someone's role ... or everyone's in the workspace' implicitly maps to the subjectType enum and hints that subjectUserId is needed for the user case, but that mapping and the role enum meanings are never spelled out.

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?

Uses a specific verb (sets) and resource (role on a sheet), and adds a scope distinction between one person and everyone in the workspace. It does not name or distinguish itself from near siblings like set_channel_role or set_file_access, but the sheet-scoped framing 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 description states a real precondition (only the sheet's owner can do this), which tells the agent when the call will succeed. It does not mention alternatives such as get_sheet_roles to inspect current roles or remove_sheet_role to revoke access, leaving routing to inference.

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