Skip to main content
Glama

Claim team roles

claim_team_roles
Destructive

Mark team roles as a person's own, the way they do it on the board's sheet: a role without 'needsApproval' is held at once; a role with it becomes a request the board's administrators confirm or decline (they are told) and counts nowhere until then — even when you, marking for somebody, are an administrator: giving outright is give_team_role. 'roles' are names as 'a,b'. With 'replace': true the list is the person's WHOLE set — roles left out are taken off and requests taken back; without it the roles are added to what they have. 'who' is 'me' by default; marking for somebody else is for the board's owner and its administrators. Answers with each role's state: held or requested.

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

Input Schema

NameRequiredDescriptionDefault
whoNoThe 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. Default 'me'.
rolesYesThe roles, by name, as 'a,b'.
replaceNotrue: the list is the person's whole set of self-marked roles.
projectKeyYesProject key, e.g. 'TH'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations flag destructiveHint=true, and the description explains precisely what is destructive: with 'replace' true, omitted roles are taken off and pending requests are taken back. It also discloses the approval workflow, that admins are notified, that pending roles 'count nowhere', and the permission gate for acting on behalf of others — all beyond what annotations convey.

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?

The purpose is front-loaded and the dense content is warranted by the approval/replace complexity, but the single run-on paragraph with nested dashes and parentheticals makes it harder to scan than it needs to be, and a few asides ('they are told') could be tightened.

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 no output schema, the description still reports the return value ('Answers with each role's state: held or requested'), covers permission requirements, prerequisite behavior around approvals, and the replace-vs-append distinction. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, but the description still adds semantics the schema lacks: 'roles' format as 'a,b', and the consequence of leaving a role out when 'replace' is true (removed, and its request withdrawn). The 'who' default of 'me' is repeated from the schema rather than extended, which keeps it off a 5.

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?

The description opens with a specific verb and resource ('Mark team roles as a person's own') and immediately distinguishes the tool from the sibling that grants roles outright ('giving outright is give_team_role'). An agent can tell it apart from set_team_role, give_team_role and decide_team_role_request without reading further.

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?

It states when a role is granted directly (no 'needsApproval') versus when it becomes a pending request, points to give_team_role for outright assignment, and names the exact conditions for marking someone else ('for the board's owner and its administrators'). It even warns that an administrator marking for another person still produces a request unless they use give_team_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