Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_approval_gates

Read-only

List configured approval gates and filter them by artifact or artifact type to review where approvals are required before designs, presets, or features proceed.

Instructions

List every configured approval gate, optionally filtered. Business+ tier.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_approval_gates"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_idNoOnly list gates on this design, preset or feature id. Omit it to list gates on every artifact.
artifact_typeNoOnly list gates on this kind of artifact: ``"design"``, ``"preset"`` or ``"feature"``. Omit it to list every kind.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / artifact_id / description
      Added value: +"Only list gates on this design, preset or feature id.  Omit it to list gates on every artifact."
    • addedInput schema / properties / artifact_type / description
      Added value: +"Only list gates on this kind of artifact: ``\"design\"``, ``\"preset\"`` or ``\"feature\"``.  Omit it to list every kind."
  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=true and destructiveHint=false, so safety is covered. The description adds a real behavioral fact not in annotations — that the tool requires Business+ tier — but says nothing about pagination, result shape, or what a gate record contains.

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, front-loaded with the action and scope, with the tier constraint appended. No filler and nothing repeated from the schema or annotations.

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?

There is no output schema, so the description is the only place an agent could learn what a listed approval gate looks like (fields, whether approvals are per-artifact, ordering). For a simple read tool with fully documented params it is minimally adequate, but that return-side gap remains.

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% and both parameters (artifact_id, artifact_type) have full enum-like descriptions in the schema, so the baseline is 3. The description's 'optionally filtered' only confirms that filtering exists without adding syntax or combination semantics.

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 ('List every configured approval gate') and notes the optional filtering. The verb 'list' cleanly separates it from siblings set_approval_gate and remove_approval_gate, though it never names them.

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?

'Optionally filtered' implies filters are optional but doesn't say when to use filtering versus listing everything, nor does it explicitly point to set_approval_gate/remove_approval_gate for mutation. The 'Business+ tier' note is a useful prerequisite, which is the strongest usage guidance present.

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