Skip to main content
Glama

List team roles

list_team_roles
Read-only

A board's team roles — what people do on its team, «Sound engineer», «Electrician» — each with 'needsApproval' (marked by a person for themselves, it waits for an administrator's yes), its holders in the order an issue for the role reaches them (an issue with the role and nobody on it goes to the first), and who asked for it and waits. Also whether you may change them ('canManage') and mark your own ('canMark'), and your own roles: held and 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>"
    },
    "name": "list_team_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectKeyYesProject key, e.g. 'TH'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description goes well beyond them: it explains that a self-marked 'needsApproval' waits for an administrator, that holders are ordered by issue routing, and that a role with no holder routes to the first. It does not mention result size or pagination, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The resource is front-loaded and every clause carries real information about the returned fields, but the whole thing is a single dense run-on sentence with nested parentheses and quoted field names, which makes it harder to parse than a short bulleted enumeration would be. It is information-dense rather than padded, but structural clarity suffers.

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?

There is no output schema, so the description must carry the return-value burden, and it does — field names, semantics of needsApproval, holder ordering, routing fallback, permission flags, and the caller's own roles. For a one-parameter read tool this is close to sufficient, with only pagination/result-size behavior left unspecified.

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 description coverage is 100% for the single required 'projectKey' parameter, so the schema already carries its meaning. The description says 'a board's' roles without ever naming projectKey or clarifying that the board is identified by that key, adding essentially no parameter meaning beyond the schema — baseline 3.

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?

The description names the specific resource (a board's team roles) and enumerates what the listing surfaces: role names, 'needsApproval', ordered holders, requesters, plus the 'canManage'/'canMark' and personal-role flags. The read verb is implicit rather than stated, but an agent can tell this apart from the mutating siblings (give_team_role, take_team_role, claim_team_roles) because it describes retrieval of state only.

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?

Usage is only implied by the enumeration of returned data — an agent infers 'read the roles before/after mutating them' rather than being told. There is no explicit when-to-use, when-not, or routing to alternatives such as decide_team_role_request for the pending requests it mentions.

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