Skip to main content
Glama

Create team

team_create

Create a team in the organization. Any member may; a member who creates one is on it as its first maintainer, an organization owner is not put on it. A team holds nothing until a wiki is granted to it (wiki_grant). Recorded in the organization's audit log.

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_create"
  }
}

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 new team's slug: lowercase letters, digits and hyphens (platform). Not "new".
titleNoThe team's name as people read it (Platform); its slug when left out.
descriptionNoWhat the team is for, in a sentence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which only say this is a non-read, non-destructive, closed-world operation), the description discloses meaningful side effects: the creator becomes the team's first maintainer, an organization owner is not added to it, no resources are attached until wiki_grant, and the action is written to the organization audit log. This is exactly the behavioral context an agent needs before mutating org structure.

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?

Three short sentences, front-loaded with the action and followed by consequences in descending importance; the wiki_grant pointer is a compact cross-reference and the audit-log note closes the loop. No filler or restatement of the title.

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?

For a four-parameter creation tool with no output schema, the description covers permissions, authorship of the resulting team, resource-less initial state, and auditability, while the schema handles all parameters. It could add what happens on slug collision or whether the call returns the created team, but nothing essential to correct invocation is missing.

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%, so slug format, title fallback, description length, and the mandatory org parameter are already fully documented in the input schema. The description adds no parameter-level meaning beyond that, which is acceptable at the baseline for fully covered schemas.

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 and resource ("Create a team in the organization") and clarifies scope by noting the team holds nothing until a wiki is granted via wiki_grant, which separates it from wiki- and access-related siblings. It stops short of explicitly contrasting with other team_* tools, but the create semantics 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 Guidelines4/5

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

"Any member may" establishes who can invoke it, and the note that a team holds no resources until wiki_grant is called gives a clear practical precondition for follow-up use. There is no explicit when-not guidance or named alternative for managing existing teams (team_update, team_addMember), leaving some routing to inference.

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