ContextLayer

create_team

Create a new team in your organization. You will be added as team lead.

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

Name	Required	Description
`name`	Yes	Team name
`objectives`	No	Team objectives as a list of strings (optional)
`description`	No	Team description (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 5, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses a key behavioral trait: the user will be added as team lead, which is a non-obvious side effect. However, it doesn't mention permissions, reversibility, or any return details, so it is informative but not comprehensive.

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 description is front-loaded with the primary action and follows with the key side effect.

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 simple create operation with no output schema and full schema coverage, the description effectively conveys the essential behavior. It might be slightly thin on return behavior or prerequisites, but it's sufficient for an agent to invoke it correctly. The side effect of becoming team lead adds valuable context.

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%, covering 'name', 'objectives', and 'description' with clear descriptions. The tool description doesn't add parameter-specific details, which is acceptable given the schema's completeness, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new team in the user's organization, using the verb 'create' and resource 'team'. It is distinguished from siblings like update_team, delete_team, and add_team_member by its focus on creation. The additional note about being added as team lead further clarifies the tool's role.

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?

The description implies usage when a new team is needed, with no explicit alternatives or exclusions. It provides clear context by scoping the operation to 'your organization' and noting the creator becomes team lead, but it doesn't name sibling tools like add_team_member for comparison. This is clear context without exclusions, meriting a 4.

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

All ContextLayer tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?