Skip to main content
Glama

Take team role

take_team_role
Destructive

Take a team role off somebody, as the board's administrator. Issues they were given for it stay theirs. Taking what they do not hold changes nothing. The board's owner and its administrators only.

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": {
      "projectKey": "<projectKey>",
      "role": "<role>",
      "who": "<who>"
    },
    "name": "take_team_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
whoYesThe person: their username or e-mail, 'me', or by Telegram — 'tg:<numeric id>' or '@handle' as their account carries it from a Telegram sign-in. Somebody named by Telegram who is not on the board is not found.
roleYesThe role, by name or id.
projectKeyYesProject key, e.g. 'TH'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the crucial side-effect detail that issues granted for the role remain with the person, plus idempotent behavior on no-op calls and the required authorization level. That is exactly the context annotations cannot express.

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?

Four short, front-loaded sentences with no filler. The authorization point is stated twice – 'as the board's administrator' and the closing 'owner and its administrators only' – a minor redundancy that keeps it from a 5.

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 destructive, three-parameter mutation with no output schema, the description covers authorization, side effects, and no-op behavior. It does not say what a successful call returns or what happens to the role's other holders, but that is a small gap.

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 100% and includes descriptions for 'who', 'role', and 'projectKey', so the schema carries the parameter burden. The description adds only indirect role semantics ('issues they were given for it stay theirs') and no syntax or format detail beyond the schema.

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 a specific verb and resource – 'take a team role off somebody' – which an agent can distinguish from give/set variants by the verb alone. It does not name or route to a sibling tool explicitly, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives clear preconditions ('The board's owner and its administrators only') and an explicit no-op case ('Taking what they do not hold changes nothing'). It never names an alternative tool such as give_team_role or set_team_role, so an agent must infer which to pick.

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