Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

remove_team_member

Destructive

Remove a tenant from a team so team-targeted scope grants stop applying while their personal organization membership remains unchanged. Requires Kiln Business.

Instructions

Remove a tenant from a team. Their personal org membership is unaffected; only team-targeted scope grants stop applying to them.

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": "remove_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 leaves.
tenant_idYesThe account taken off the team.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / team_id / description
      Added value: +"The team the person leaves."
    • addedInput schema / properties / tenant_id / description
      Added value: +"The account taken off the team."
  2. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false. The description adds valuable behavioral detail beyond those hints by explaining that personal org membership remains intact while only team-targeted scope grants stop applying, and it states the Kiln Business plan prerequisite.

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 two tight sentences with the core effect front-loaded and the prerequisite clearly separated. Every sentence adds useful information without repetition.

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 destructive membership-removal tool with annotations covering safety and a fully described schema, the description is nearly complete: it explains scope effects and the plan requirement. It does not mention the approval/repeat-call behavior around ask_id, though that is covered in the schema.

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 coverage is 100%, so team_id and tenant_id are already well described in the schema. The description reinforces the team/tenant relationship but does not add meaning beyond the schema, and the approval flow for ask_id is documented only in the schema.

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 uses a specific verb and resource: 'Remove a tenant from a team.' It also distinguishes the action from org membership removal by stating that personal org membership is unaffected and only team-targeted scope grants stop applying.

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?

It gives clear usage context: remove a tenant from a team, with the prerequisite that the organisation must be on Kiln Business. It also implies a contrast with personal org removal, though it does not explicitly name a sibling tool as the alternative.

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