Skip to main content
Glama

Give team role

give_team_role

Give a team role to somebody on the board, as its administrator: held at once, never asked for a yes — giving a role somebody asked for IS the yes, and tells them. Giving it twice keeps their place in the order. Issues for the role with nobody on them reach its holder of longest standing. The board's owner and its administrators only; the person must be on the board.

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": "give_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

A3.8/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes well beyond that, disclosing consent semantics ('never asked for a yes — giving a role somebody asked for IS the yes'), a notification side effect ('tells them'), idempotent behavior, and issue-routing consequences for vacant roles. The prose is cryptic in places, but the behavioral disclosure is substantive.

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?

Wait — rescored: the paragraph front-loads the action and actor, then packs prerequisites, consent, idempotency, and vacancy routing into three sentences with no filler. The em-dash construction is dense but each clause carries distinct operational information.

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 three-parameter mutation with no output schema, it covers the essentials: who may call it, who the target must be, consent behavior, notification, repeat-call semantics, and downstream issue assignment. Only the return value/shape of the response is left implicit, which is minor absent an output schema.

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%, so 'who', 'role', and 'projectKey' are already documented, including the Telegram handle forms. The description adds only the board-membership constraint on the person, which is a meaningful but small increment over 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 ('Give a team role to somebody on the board') and narrows it with an actor constraint ('as its administrator'), so the agent knows this is an admin granting a role to another person. It never names which sibling to use instead (set_team_role, take_team_role, claim_team_roles, decide_team_role_request), so differentiation is inferred 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?

Gives a real precondition set — 'The board's owner and its administrators only; the person must be on the board' — which tells the agent when the call is legal, and the idempotency note ('Giving it twice keeps their place in the order') clarifies repeat use. But there is no explicit routing against the many sibling role tools, so the agent must guess when this is preferable to set_team_role or claim_team_roles.

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