Skip to main content
Glama

Роли участников

get_workspace_roles
Read-onlyIdempotent

Возвращает роли аккаунта с их правами и числом участников на каждой роли. Значения прав: allowed — разрешено, partially — только свои объекты, forbidden — запрещено. Сам инструмент только читает; создать или изменить роль — save_workspace_role, удалить — delete_workspace_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_id": "<workspace_id>"
    },
    "name": "get_workspace_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered and restating read-only is mildly redundant. The description earns credit by disclosing return semantics not captured anywhere else (per-role permission values and member counts) and by defining the permission enum meanings allowed/partially/forbidden.

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

Conciseness5/5

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

Three short sentences, front-loaded with the purpose, then the value semantics, then the sibling routing. No filler and no repetition of the title.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description supplies what the schema cannot: the shape of the result (roles with permissions and member counts) and the meaning of permission values. Only a minor gap remains, such as whether default/system roles are included alongside custom ones.

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?

There is a single parameter with 100% schema description coverage, including the hint that the ID comes from workspace://list. The description adds nothing further about workspace_id, which is acceptable given the schema already carries the meaning.

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

Purpose5/5

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

States a specific verb and resource ('Возвращает роли аккаунта') plus what is returned: permissions and the number of members per role. It also explicitly separates itself from save_workspace_role and delete_workspace_role, so an agent can distinguish it from the mutation siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-not guidance ('Сам инструмент только читает') and names the correct alternatives with their conditions: create/modify → save_workspace_role, delete → delete_workspace_role. Routing to the right sibling is fully determined by the text.

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