Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

revoke_scope

Destructive

Revoke a personal or team-targeted scope grant in Kiln to remove read, push, release, or admin access for an organization.

Instructions

Revoke a scope grant. Supply either tenant_id (to remove a personal grant) or team_id (to remove a team-targeted grant).

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>",
      "scope_key": "<scope_key>",
      "capability": "<capability>"
    },
    "name": "revoke_scope"
  }
}

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 grant was made in.
team_idNoThe team whose grant is removed. Give exactly one of ``tenant_id`` and ``team_id``.
scope_keyYesThe grant's scope key, exactly as it was granted.
tenant_idNoThe account whose personal grant is removed. Give exactly one of ``tenant_id`` and ``team_id``.
capabilityYesThe capability revoked: ``"read"``, ``"push"``, ``"release"`` or ``"admin"``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / capability / description
      Added value: +"The capability revoked: ``\"read\"``, ``\"push\"``, ``\"release\"`` or ``\"admin\"``."
    • addedInput schema / properties / org_id / description
      Added value: +"The org the grant was made in."
    • addedInput schema / properties / scope_key / description
      Added value: +"The grant's scope key, exactly as it was granted."
    • addedInput schema / properties / team_id / description
      Added value: +"The team whose grant is removed.  Give exactly one of ``tenant_id`` and ``team_id``."
    • addedInput schema / properties / tenant_id / description
      Added value: +"The account whose personal grant is removed.  Give exactly one of ``tenant_id`` and ``team_id``."
  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 and readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: the Kiln Business plan requirement and the mutually exclusive grant targeting. It does not say whether a revocation is reversible or what happens to the approval/ask flow, but the core behavioral facts are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and followed by the targeting rule and prerequisite. The targeting sentence partially duplicates the schema, which is the only waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter destructive mutation with no output schema, the description covers purpose, grant targeting, and the plan-level prerequisite, while the schema handles the approval flow and capability enumeration. An agent has enough to call it correctly without further reading.

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 each parameter, including the ask_id approval round-trip and the capability values, is documented in the schema. The description only restates the tenant_id/team_id exclusivity already declared in both property descriptions, adding no syntax or format detail beyond 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 opens with a specific verb and resource ("Revoke a scope grant") and immediately distinguishes the two targeting modes, personal vs team. An agent can tell this is the inverse of grant_scope without inspecting 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 Guidelines4/5

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

It states the selection rule between tenant_id and team_id and adds the operational prerequisite that the organisation must be on Kiln Business. It does not explicitly name grant_scope or list_scopes as alternatives, so routing is implied rather than spelled out.

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