Skip to main content
Glama

graph_get_team

Retrieves a team's details by team ID, including its archived status. Use it to check team information before managing members, channels, or collaboration settings.

Instructions

Get a team's details, including whether it is archived.

Args: team_id: The team ID (from graph_list_teams).

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": "graph_get_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It says 'Get' (implying a read) but does not disclose read-only semantics, auth requirements, error behavior for an invalid ID, or what fields are returned beyond archived status.

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 behavior in the first sentence, followed by a tidy Args block. No filler, though the Args section repeats the parameter name and is slightly verbose given the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read with no output schema, the description is mostly adequate: it states what is returned (team details, archived flag) and where the ID comes from. It stops short of covering response shape or error/edge behavior, which a no-annotation tool should ideally include.

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 has 0% description coverage, so the description must compensate for the single parameter. It does provide meaning beyond the bare 'string' type by naming it 'The team ID (from graph_list_teams),' which tells the agent where to get the value. That is sufficient for a lone identifier, though no format or validation detail is given.

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 (get) and resource (team), and adds scope ('details, including whether it is archived'). This distinguishes it from graph_list_teams, which lists teams rather than retrieving one.

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?

Implies the tool is for retrieving a single team's details when you have an ID, and helpfully points to graph_list_teams as the source of team_id. However, it never explicitly states when to use this versus listing teams or other get_* siblings, nor any preconditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools