Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

create_team

Creates a team sub-group inside an organization on Kiln Business, requiring the org ID, a display name, and a unique slug.

Instructions

Create a team (sub-group) inside an org.

Needs the organisation to be on Kiln Business.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe team's display name. Must not be empty.
slugYesThe team's short name, unique within the org. Must not be empty.
ask_idNoThe id an earlier ``APPROVAL_REQUIRED`` answer returned. Pass it on the repeat call to learn whether the person approved; omit it on the first call.
org_idYesThe org the team is made in.
created_byNoWho is making the team, recorded on it. On Kiln's hosted server it is read from the signed-in session.
descriptionNoA short description of the team. Empty by default. Default: "".
parent_team_idNoA team to nest this one under. Recorded, but not yet used by the capability check. Omit it for a top-level team.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.1
    • addedInput schema / properties / ask_id
      Added value: +{
+  "description": "The id an earlier ``APPROVAL_REQUIRED`` answer returned. Pass it on the repeat call to learn whether the person approved; omit it on the first call.",
+  "title": "Ask Id",
+  "type": "string"
+}
    • addedInput schema / properties / created_by / description
      Added value: +"Who is making the team, recorded on it.  On Kiln's hosted server it is read from the signed-in session."
    • changedInput schema / properties / description / description
      Previous value: -"Default: \"\"."New value: +"A short description of the team.  Empty by default. Default: \"\"."
    • addedInput schema / properties / name / description
      Added value: +"The team's display name.  Must not be empty."
    • addedInput schema / properties / org_id / description
      Added value: +"The org the team is made in."
    • addedInput schema / properties / parent_team_id / description
      Added value: +"A team to nest this one under.  Recorded, but not yet used by the capability check.  Omit it for a top-level team."
    • addedInput schema / properties / slug / description
      Added value: +"The team's short name, unique within the org.  Must not be empty."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, non-destructive, closed-world mutation, and the description usefully adds the Kiln Business plan prerequisite. It omits other behavior an agent would want: what error occurs when a slug collides within the org, that an APPROVAL_REQUIRED answer may need a repeat call, and what happens to child teams when nesting via parent_team_id.

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 sentences, front-loaded with the action and scope, with the plan prerequisite as the second line. Nothing redundant or repeated from the name or schema.

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?

For a 7-parameter mutation with no output schema, the description covers the domain and the plan gate but leaves the approval round-trip, uniqueness failure mode, and permission requirements entirely to the schema. It is adequate but not self-sufficient.

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% and every parameter carries its own description, including the ask_id approval protocol and parent_team_id's caveat that it is recorded but not used by the capability check. The description adds no parameter-level meaning of its own, so the baseline 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?

States a specific verb and resource (create a team) and clarifies the domain noun with '(sub-group) inside an org', which disambiguates from generic 'team' usage. It does not explicitly contrast with siblings such as create_org or delete_team, so an agent must infer the distinction from names alone.

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

Usage Guidelines3/5

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

Provides one real usage gate: the organisation must be on Kiln Business. There is no guidance on when to prefer this over create_org, when not to create a team, or how the approval flow (ask_id in the schema) should be sequenced, so usage is only partially implied.

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

Deploy Server

Other Tools