Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_features

Read-only

Lists the current version of every known feature, scoped to a design or portfolio, with optional archived items.

Instructions

List the latest version of every known feature.

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

Input Schema

NameRequiredDescriptionDefault
design_idNoScope to a single design (plus portfolio-wide).
portfolio_onlyNoWhen True, return only design-agnostic features regardless of ``design_id``. Default: false.
include_archivedNoWhen True, include features hidden by ``archive_feature``; default False filters them out. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"Scope to a single design (plus portfolio-wide)."
    • changedInput schema / properties / include_archived / description
      Previous value: -"Default: false."New value: +"When True, include features hidden by ``archive_feature``; default False filters them out. Default: false."
    • changedInput schema / properties / portfolio_only / description
      Previous value: -"Default: false."New value: +"When True, return only design-agnostic features regardless of ``design_id``. Default: false."
  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 a read-only, non-destructive, closed-world listing, so the safety profile is covered. The description adds the Kiln Pro entitlement requirement, which is genuinely beyond the annotations, but says nothing about result size, pagination, or default scoping behavior.

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, scope first and the entitlement caveat second. No filler; every line carries information.

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 simple read-only list with zero required parameters and a fully documented schema, the description covers purpose and the access prerequisite. With no output schema, though, the shape of returned feature entries (and whether results are paginated) is left unexplained.

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 the parameter descriptions already explain the design_id/portfolio_only interaction and archived filtering. The description contributes no additional parameter meaning, 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 ('List ... every known feature') and narrows scope to the latest version, which separates it from list_feature_versions and list_feature_releases. It does not explicitly name a sibling alternative, keeping it short of a 5.

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 a real prerequisite (tier gating) that an agent must know before calling, but there is no when-to-use guidance and no routing against siblings like get_feature, list_feature_branches, or list_feature_versions.

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