Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_capability

Read-only

Dry-run the cloud permission check to verify whether a tenant can read, push, release, or administer a scoped resource before the actual authorization request runs.

Instructions

Dry-run the permission check the cloud will run.

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

Input Schema

NameRequiredDescriptionDefault
org_idYesThe org the check runs in.
scope_keyYesWhat the permission is for, for example ``design:<id>`` or ``*``.
tenant_idYesThe account whose permission is checked.
capabilityYesThe capability checked: ``"read"``, ``"push"``, ``"release"`` or ``"admin"``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so safety is covered. The description adds two pieces of context not in the structured fields: the result mirrors what the cloud will actually decide (a dry-run, not an ad-hoc local estimate), and it requires a Kiln Business entitlement. It omits what a denial looks like or whether the check has side effects on quota.

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 lines, both front-loaded: what it does first, prerequisite second. No filler, no restatement of the name or title.

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?

All four required parameters are documented in the schema and there is no output schema, so the description is nearly complete for invocation. What it lacks is any hint of the return shape (granted vs denied, and whether a reason is included), which matters for a check tool whose whole value is the answer.

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 the schema already explains org_id, tenant_id, scope_key with examples, and enumerates capability values. The description adds no parameter meaning beyond that, 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: 'Dry-run the permission check the cloud will run.' An agent can tell this simulates an authorization decision rather than performing an action. It doesn't name a sibling to contrast with (e.g., may_i_print or check_autonomy), so differentiation is left to the reader.

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?

'Dry-run' implies pre-flight use before attempting an operation, and 'Needs Kiln Business' states a prerequisite, which is genuinely useful. However, it never says when to prefer this over adjacent permission tools like may_i_print, check_autonomy, or check_my_tier, nor what to do when the check fails.

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