Skip to main content
Glama

Get team

team_get
Read-only

One team, by slug: its id, title, description and members (userId, whether each is a maintainer or a member of the team, who added them and when), whether the caller may change it, and the wikis it is granted, each at its level (wikis: name, level read, write or admin; only the wikis the caller may see).

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": {
      "slug": "<slug>",
      "org": "<org>"
    },
    "name": "team_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.
slugYesThe team's slug, as team_list gives it (platform).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / org / description
      Previous value: -"slug of the organization whose people, teams and access to read. Required on every call, even when only one organization is listed; a path never names it."New value: +"slug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it."
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so the safety profile is covered structurally. The description does add real behavioral context beyond that: the caller-relative permission field ("whether the caller may change it") and the visibility filter ("only the wikis the caller may see"), which tell the agent results are scope-dependent. However, it says nothing about failure behavior for a nonexistent slug or whether member lists are truncated.

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?

It is a single sentence with a strong, front-loaded opening ("One team, by slug"), but the payload is stuffed into nested parentheticals that are hard to parse in one pass and would read better as listed fields. Every clause is substantive, so the weakness is structure rather than waste.

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 bears the burden of describing the return value, and it does so thoroughly: identity fields, member entries with role and attribution, caller mutation rights, and per-wiki access levels. The notable remaining gap is error behavior for a bad or unauthorized slug, and possible truncation of long member lists.

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%: both org and slug are documented in the schema with a pattern, an enum, and a pointer to team_list as the slug source. The description only restates that the lookup key is a slug, adding no syntax or format meaning beyond what the schema already provides, so the baseline of 3 applies.

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 opens with a specific verb+resource+key: "One team, by slug," immediately signaling singular retrieval rather than a listing. It then enumerates the exact payload (id, title, description, members, permissions, wikis). It never names team_list explicitly, so sibling differentiation is only implicit via "One team" versus a collection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no exclusion of alternatives, and no stated precondition beyond the slug being required. The only workflow hint ("as team_list gives it") lives in the schema, not the description, so an agent must infer that this is the follow-up call after listing teams.

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