Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

add_team_member

Destructive

Adds an account to a team and sets its role as member or maintainer, so you can manage Kiln Business team membership.

Instructions

Add tenant_id to team_id.

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": {
      "team_id": "<team_id>",
      "tenant_id": "<tenant_id>"
    },
    "name": "add_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoThe team role: ``"maintainer"`` or ``"member"`` (the default). Any other value is refused. Default: "member".
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.
team_idYesThe team the person joins.
added_byNoWho is adding the member, recorded on the membership. On Kiln's hosted server it is read from the signed-in session.
tenant_idYesThe account added to the team.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • addedInput schema / properties / added_by / description
      Added value: +"Who is adding the member, recorded on the membership.  On Kiln's hosted server it is read from the signed-in session."
    • 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"
+}
    • changedInput schema / properties / role / description
      Previous value: -"Default: \"member\"."New value: +"The team role: ``\"maintainer\"`` or ``\"member\"`` (the default). Any other value is refused. Default: \"member\"."
    • addedInput schema / properties / team_id / description
      Added value: +"The team the person joins."
    • addedInput schema / properties / tenant_id / description
      Added value: +"The account added to the team."
  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 readOnlyHint=false and destructiveHint=true, so the agent knows this mutates state. The description adds the plan-entitlement requirement, which is genuinely valuable context not present in structured fields. It omits, however, the APPROVAL_REQUIRED / ask_id round-trip that the schema hints at, which is the most important behavioral quirk of this mutation.

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, the operation stated first and the prerequisite second, with zero filler. Nothing could be removed without losing information.

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?

With no output schema and a moderately complex five-parameter mutation, the description covers the entitlement gate but says nothing about what a successful call returns or how the two-call approval pattern works. The rich schema compensates for parameter details, but the description alone would leave an agent unprepared for an approval-required response.

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 role enums, ask_id semantics, added_by provenance, and tenant_id meaning are all fully documented in the schema itself. The description adds no meaning beyond repeating the team_id and tenant_id names, 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?

The description states a specific verb and resource ('Add *tenant_id* to *team_id*') and even names the two identifier parameters involved, so the operation is unambiguous. It does not, however, differentiate itself from the closely related sibling 'add_org_member', leaving the agent to infer the org-vs-team distinction.

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?

It gives one real prerequisite — 'Needs the organisation to be on Kiln Business' — which tells the agent a plan gate exists. But there is no guidance on when to prefer this over add_org_member or apply_role_template, and no mention of the approval flow implied by the ask_id parameter.

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