Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fingerprint_feature

Read-only

Return the content-addressed fingerprint of a feature version to identify its exact state for reliable version tracking. Requires Kiln Pro.

Instructions

Return the content-addressed fingerprint of a feature version.

Needs Kiln Pro.

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": {
      "feature_version_id": "<feature_version_id>"
    },
    "name": "fingerprint_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
feature_version_idYesUUID of the version to fingerprint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / feature_version_id / description
      Added value: +"UUID of the version to fingerprint."
  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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value with the entitlement requirement ('Needs Kiln Pro') and the fact that the result is content-addressed (deterministic hash), but it says nothing about failure modes when the license is absent or whether fingerprints are stable across renames.

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 with zero waste; the operation is front-loaded and the entitlement caveat follows immediately.

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 single-parameter read tool with full schema coverage and annotations, the essentials are present. However, there is no output schema, and the description does not indicate what form the fingerprint takes or that the agent can use check_my_tier/upgrade_kiln to resolve the Kiln Pro requirement — a small but real gap.

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 single parameter (feature_version_id as a UUID) is fully documented in the schema. The description adds nothing beyond confirming the argument denotes a feature version, so the baseline 3 is appropriate.

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 precise verb and resource: 'Return the content-addressed fingerprint of a feature version.' The 'feature version' qualifier implicitly separates it from the sibling fingerprint_model, though it never names that sibling explicitly.

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?

The prerequisite 'Needs Kiln Pro' is useful gating information, but there is no statement of when an agent should fingerprint a feature version versus alternatives like verify_feature_release, sign_feature_release, or fingerprint_model. Usage is only implied by the tool name.

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