Skip to main content
Glama

Get team

get_team
Read-onlyIdempotent

Get one team: its name, description, icon and colour, and whether conversations are auto-assigned to its members.

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": {
      "team_id": "<team_id>"
    },
    "name": "get_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.
team_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "id",
      -  "name",
      -  "description",
      -  "allow_auto_assign"
      -]New value: +[
      +  "id",
      +  "name",
      +  "description",
      +  "allow_auto_assign",
      +  "icon",
      +  "icon_color"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds that it returns identity and configuration fields including auto-assignment status, but says nothing about error behaviour for unknown ids or whether the fields parameter affects the response shape.

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?

One sentence, front-loaded with the operation and immediately followed by the returned attributes. Nothing is redundant and no filler is present.

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?

With no output schema, the description usefully names the returned attributes, which is the main completeness risk for this tool. Two simple parameters and full annotation coverage mean little else is required; only the fields-projection behaviour could be made clearer.

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 50%: fields is fully described in the schema, while team_id carries no schema description but is self-explanatory as a positive integer. The description's enumeration of name, description, icon, colour and auto-assign maps neatly onto the fields enum, adding modest context but no format or usage detail beyond 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?

"Get one team" gives a specific verb and resource, and "one" implicitly contrasts with list_teams, so an agent can tell retrieval-by-id from listing. It stops short of naming a sibling explicitly, but the resource and cardinality are unambiguous.

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: the singular "one team" plus a required team_id signals that this is a lookup when an id is already known, versus list_teams for discovery. There is no explicit when/when-not guidance or any mention of alternatives like get_team_report or list_team_members.

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