Skip to main content
Glama

Create team

create_team
Destructive

Create a team. Team names are stored in lowercase.

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

Input Schema

NameRequiredDescriptionDefault
iconNoIcon shown beside the team in the sidebar and assignment menus.
nameYes
icon_colorNoColour of the team icon.
descriptionNo
allow_auto_assignNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / icon
      Added value: +{
      +  "description": "Icon shown beside the team in the sidebar and assignment menus.",
      +  "enum": [
      +    "people-team",
      +    "headphones-sound-wave",
      +    "chat",
      +    "call",
      +    "mail",
      +    "tag",
      +    "credit-card-person",
      +    "content-settings",
      +    "lock-shield",
      +    "star-emphasis",
      +    "heart-handshake",
      +    "building-bank",
      +    "globe",
      +    "flash-on",
      +    "book",
      +    "wand",
      +    "settings",
      +    "alert",
      +    "calendar",
      +    "briefcase"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / icon_color
      Added value: +{
      +  "description": "Colour of the team icon.",
      +  "enum": [
      +    "slate",
      +    "blue",
      +    "green",
      +    "amber",
      +    "red",
      +    "violet",
      +    "teal",
      +    "pink"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent mutation with destructiveHint=true, so the safety profile is largely covered. The description adds one genuine behavioral detail beyond that – name normalization to lowercase – but says nothing about permission requirements, duplicate-name behavior, or whether the new team starts empty. Notably it does not reconcile its benign 'create' framing with the destructiveHint annotation.

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?

Two short sentences with no filler; the core action comes first and the normalization caveat follows immediately. Every sentence earns its place.

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 five-parameter mutation tool with annotations covering the safety profile and no output schema, the definition covers the essential action and one key behavioral quirk. Gaps remain around permissions, duplicate handling, and the three undocumented parameters, so it is close to but not fully complete.

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 only 40%; icon and icon_color are documented in the schema, while name, description, and allow_auto_assign are bare. The description partially compensates by revealing that 'name' is stored lowercased, which is real parameter-level meaning not present in the schema, but the remaining undocumented parameters get no help.

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 states a specific verb and resource ('Create a team'), which is immediately distinguishable from siblings like update_team, delete_team, get_team, and list_teams. It does not explicitly name or contrast those siblings, 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 Guidelines2/5

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

There is no guidance on when to use this versus alternatives such as add_team_member or update_team, no stated prerequisites (admin role, seat limits), and no note on what to do when a team with that name already exists. Usage is only implied by the verb.

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