Skip to main content
Glama

Set team role

set_team_role
Destructive

Make a team role on a board, or change one: named by 'role' (its name, any case, or id) — made when the board has none by that name. 'needsApproval': true makes a person who marks the role for themselves wait for an administrator's yes (for roles safety rests on — «Electrician»); false gives the role to everybody who was waiting. 'rename' gives an existing role a new name. Left out, either stays as it is. The board's owner and its administrators only. Answers with the role, its holders and who waits.

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

Input Schema

NameRequiredDescriptionDefault
roleYesThe role's name, e.g. 'Электрик' (or its id, to change one).
renameNoA new name for an existing role.
projectKeyYesProject key, e.g. 'TH'.
needsApprovalNoWhether a person marking it for themselves waits for an administrator's yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true and readOnly=false; the description adds owner/admin-only authorization, approval workflow semantics, the side effect of releasing waiting holders when needsApproval=false, and return contents. It does not explicitly warn about irreversibility, but the key behavioral context beyond annotations is present.

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?

Front-loads the create/update purpose and packs necessary conditions into a compact paragraph. Dense punctuation and long clauses reduce readability slightly, but no sentence is wasted.

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 mutation tool with annotations and no output schema, the description covers authorization, approval side effects, rename behavior, and return shape. Minor gaps around error cases or exact response structure remain, but it is largely complete.

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%, so the baseline is 3; the description adds case-insensitive name/id matching for role, the creation-vs-update condition, and precise effects of needsApproval and rename. projectKey remains only schema-documented, but most parameters gain meaning.

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: 'Make a team role on a board, or change one,' with scope tied to role name/id. It does not explicitly name sibling alternatives such as give_team_role or claim_team_roles, so differentiation is implicit rather than stated.

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?

Explains the creation condition (when the board has no role by that name), update behavior, and the owner/admin permission restriction. It does not say when to choose this over give_team_role, take_team_role, claim_team_roles, or decide_team_role_request, so alternative selection is left 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