Skip to main content
Glama

Coline

Create a team

create_team

Creates a team in a team workspace, with its own drive and channel.

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": {
      "workspace": "<workspace>",
      "name": "<name>"
    },
    "name": "create_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoAn emoji.
nameYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo

Output Schema

NameRequiredDescriptionDefault
teamYes
driveIdYes
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare this as a non-read-only, non-destructive, non-idempotent, closed-world creation operation. The description adds important behavioral context beyond the annotations by disclosing that creating a team also provisions its own drive and channel, a cascading side effect an agent should know about.

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?

The description is a single front-loaded sentence with no wasted wording. It states the action and side effects efficiently.

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?

The output schema, annotations, and schema partially cover return behavior, safety, and required inputs, and the description adds the important drive/channel side effect. However, it omits permission prerequisites, duplicate-name behavior, and parameter semantics for two undocumented schema fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description provides no parameter-level meaning at all. It does not explain the required team name, workspace slug usage, optional icon, or description fields, leaving the agent dependent on the partially documented 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?

The description uses a specific verb and resource: it creates a team, scoped to a team workspace. It also notes the team comes with its own drive and channel, which helps distinguish it from generic workspace creation, though it does not explicitly contrast with sibling tools such as create_workspace.

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?

The description states what the tool does but gives no explicit guidance on when to use it instead of alternatives such as create_workspace or other team-related tools. The only context is the implied requirement that a team workspace exists.

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