Skip to main content
Glama

Coline

Sheet roles

get_sheet_roles
Read-onlyIdempotent

The roles set on a sheet (they narrow Drive access, never widen it) and the person's own role.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
roleYes
grantsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful piece of domain behavior not in annotations — that sheet roles narrow Drive access and never widen it — but says nothing about permissions required, behavior when no roles are set, or how the caller's own role is resolved.

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 substantive qualifier about access narrowing is placed up front in the parenthetical. The phrasing is slightly fragmented, reading as a sentence fragment rather than a statement of what the tool returns, but nothing 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 and annotations are rich, so return format and safety need not be restated. However, for a tool with many role-related siblings, the description omits the one thing structured fields cannot supply: that this is the read counterpart to set_sheet_role/remove_sheet_role.

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 description coverage is 100% and both parameters (sheetId, workspace) are documented inline with sourcing hints. The description contributes no additional meaning about either parameter, so the baseline of 3 applies.

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 is a noun phrase rather than a verb, but it does identify the resource: the roles set on a sheet plus the requesting person's own role. It never states the operation explicitly (retrieve/list) and gives no differentiation from siblings like set_sheet_role or remove_sheet_role, so an agent must lean on the name to know this is a read.

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 set_sheet_role or remove_sheet_role. The parenthetical about access narrowing is a semantic note about the domain, not a usage rule.

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