Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

remove_org_member

Destructive

Remove a member from an organization and revoke all permission scopes they held in that org; the organization must be on Kiln Business.

Instructions

Remove a member and every permission scope they held inside org_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": {
      "org_id": "<org_id>",
      "tenant_id": "<tenant_id>"
    },
    "name": "remove_org_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.
org_idYesThe org the member leaves.
tenant_idYesThe account removed, along with every permission scope it held in the org.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds valuable behavioral context by stating that all permission scopes held by the member in the org are removed and that the organisation must be on Kiln Business.

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 core destructive action and followed by the prerequisite. There is no redundant or filler language.

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 org-membership operation, the description gives the key scope of destruction and the licensing prerequisite, while schema annotations cover safety hints and parameter details. It omits explicit sibling routing and approval-workflow context, but the ask_id schema description covers the approval flow.

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 org_id, tenant_id, and ask_id are already well documented in the input schema. The description reinforces org-level scope but does not add parameter meaning beyond what the schema provides.

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 states a specific verb and resource: remove a member, with the added scope of every permission scope they held inside a named org. This clearly distinguishes it from remove_team_member and scope-level tools like revoke_scope without needing to open the schema.

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 provides a useful licensing prerequisite (Kiln Business) but does not explicitly say when to use this tool versus remove_team_member, revoke_scope, or list_org_members. Usage is implied by the org-member removal wording rather than actively guided.

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