Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_feature_releases

Read-only

Lists signed feature releases and their reference IDs, with optional filtering by feature and inclusion of retired releases.

Instructions

List signed feature releases — and the ids that reference them.

Needs Kiln Pro.

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_feature_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
feature_idNoRestrict to one feature (default: all).
include_retiredNoWhen true, retired releases are listed too. Off by default. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / feature_id / description
      Added value: +"Restrict to one feature (default: all)."
    • changedInput schema / properties / include_retired / description
      Previous value: -"Default: false."New value: +"When true, retired releases are listed too.  Off by default. Default: false."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description's contribution is the Kiln Pro entitlement requirement, which is genuinely beyond the annotations, but it is silent on result ordering, pagination, or whether unsigned releases are excluded from the response.

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?

Two short fragments with the action front-loaded and a prerequisite isolated on its own line; nothing is padded. It is arguably terse to the point of under-specification, but not wasteful.

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?

For a two-parameter, zero-required read tool with full schema coverage and no output schema, the definition covers the essentials plus the tier requirement. It still leaves open what a returned entry contains and how 'signed' versus retired releases interact, which matters given the dense release-related sibling cluster.

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%, with both feature_id ('default: all') and include_retired ('Off by default') fully documented. The description adds no further meaning about these filters, so 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 ('List signed feature releases'), and the qualifier 'signed' usefully narrows the scope compared with siblings like list_feature_versions or list_feature_branches. It does not explicitly name a sibling, so an agent must infer the boundary from the noun phrase alone.

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?

'Needs Kiln Pro' gives one concrete prerequisite for calling it, which is real guidance. However, there is no statement of when to prefer this over list_feature_versions, list_design_releases, or verify_feature_release, so the routing decision remains implicit.

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