Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

manage_fair_evidence_bundle

Destructive

Export, verify, or import portable FAIR evidence bundles so teams can transfer configuration evidence across air-gapped systems.

Instructions

Portable FAIR evidence bundles for air-gapped team transfer.

Needs Kiln Enterprise.

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": {
      "action": "<action>"
    },
    "name": "manage_fair_evidence_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes``export``, ``verify`` or ``import_bundle`` (case-insensitive); anything else is refused with ``INVALID_ACTION``.
bundle_pathNoFor ``export``, where to write the bundle; empty writes it to Kiln's local FAIR export folder under a digest-based name. For ``verify`` and ``import_bundle``, required: the bundle file to read. Default: "".
evidence_case_idNo``export`` only, required: the configuration evidence case to package. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / action / description
      Added value: +"``export``, ``verify`` or ``import_bundle`` (case-insensitive); anything else is refused with ``INVALID_ACTION``."
    • changedInput schema / properties / bundle_path / description
      Previous value: -"Default: \"\"."New value: +"For ``export``, where to write the bundle; empty writes it to Kiln's local FAIR export folder under a digest-based name. For ``verify`` and ``import_bundle``, required: the bundle file to read. Default: \"\"."
    • changedInput schema / properties / evidence_case_id / description
      Previous value: -"Default: \"\"."New value: +"``export`` only, required: the configuration evidence case to package. Default: \"\"."
  2. Addedv1.5.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description does not explain what is destructive, which action mutates state, or what happens during import. The Enterprise prerequisite is useful context, but it does not clarify the tool's operational effects.

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?

The description is two short sentences with no wasted wording, and the licensing requirement is isolated clearly. It is concise, though the front-loaded sentence is a noun phrase rather than a clear statement of what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-action, destructive tool with no output schema, the description omits what export, verify, and import_bundle actually do and what side effects an agent should expect. The schema covers the action names, but the definition does not provide enough context to safely distinguish the operations.

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%, so the action, bundle_path, and evidence_case_id semantics are fully documented in the schema. The main description adds no additional parameter guidance, so this sits at the baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (FAIR evidence bundles) and a use context (air-gapped team transfer), but it never states the action verbs. It does not say that the tool exports, verifies, or imports bundles, so an agent must infer the operation from the tool name and schema.

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 phrase 'air-gapped team transfer' implies when the tool is useful, and 'Needs Kiln Enterprise' provides a prerequisite. However, it gives no explicit guidance on choosing between actions or when to use this versus sibling FAIR management tools such as manage_fair_registry or manage_fair_characteristics.

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