Skip to main content
Glama

Decide team role request

decide_team_role_request
Destructive

Confirm or decline somebody's request for a team role that needs an administrator's yes (list_team_roles shows who waits under each role). 'decision': 'approve' — they hold the role from now, at the back of its holders; 'reject' — the request goes. They are told either way, and it is written to the board's journal. 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>",
      "decision": "<decision>"
    },
    "name": "decide_team_role_request"
  }
}

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.
decisionYes'approve' or 'reject'.
projectKeyYesProject key, e.g. 'TH'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds substantial context beyond them: approval places the person at the back of the role's holders, rejection deletes the request, the requester is notified, and the action is journaled on the board. Permission scope (owner/admins only) is also disclosed. It could still note irreversibility of a rejection more bluntly.

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-loaded with the core action and its scope, then effects, then permissions. The parenthetical on list_team_roles is slightly interruptive and the sentence on approval ordering is dense, but nothing is wasted.

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?

For a destructive, permission-gated membership mutation with no output schema, the description covers who may call it, what each decision does, side effects (notification, journaling), and where to find pending requests. An agent has everything needed to call it correctly.

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 earns a bump by explaining the concrete effect of each 'decision' value, which the schema only enumerates as 'approve' or 'reject'. 'role' and 'who' semantics are left entirely to the schema.

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 precise verb pair (confirm/decline) and a precise resource (a team role request requiring an administrator's yes), and cross-references list_team_roles for discovery. This distinguishes it from direct-grant siblings like give_team_role and set_team_role.

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?

Points to list_team_roles as the way to find who is waiting under each role, and states the access precondition (board owner and administrators only). It does not explicitly say when to prefer give_team_role over this, but the 'request that needs an administrator's yes' framing implies the boundary.

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