Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

store_credential

Encrypts and stores a secret credential such as an API key or printer password at rest, returning only metadata so the plaintext is never exposed.

Instructions

Encrypt and store a credential (API key, webhook secret, etc.).

        The value is encrypted at rest using PBKDF2 + XOR stream encryption.
        Only metadata is returned — the plaintext is never exposed.

        Args:
            credential_type: Type of credential (api_key, webhook_secret,
                stripe_key, marketplace_token, printer_password).
            value: The plaintext secret to store.
            label: Human-readable description.

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": {
      "credential_type": "<credential_type>",
      "value": "<value>"
    },
    "name": "store_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoHuman-readable description. Default: "".
valueYesThe plaintext secret to store.
credential_typeYesType of credential (api_key, webhook_secret, stripe_key, marketplace_token, printer_password).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / credential_type / description
      Added value: +"Type of credential (api_key, webhook_secret, stripe_key, marketplace_token, printer_password)."
    • changedInput schema / properties / label / description
      Previous value: -"Default: \"\"."New value: +"Human-readable description. Default: \"\"."
    • addedInput schema / properties / value / description
      Added value: +"The plaintext secret to store."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / label / default
      Removed value: -""
    • addedInput schema / properties / label / description
      Added value: +"Default: \"\"."
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, closed-world write, and the description adds genuinely new behavioral context: PBKDF2 + XOR stream encryption at rest and the guarantee that only metadata is returned while plaintext is never exposed. It stops short of covering idempotency/overwrite semantics or required permissions, which is why it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The behavioral paragraph is front-loaded and earns its place, but the trailing 'Args' block duplicates what the input schema already documents for all three parameters and could be removed without information loss.

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

Completeness4/5

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

For a three-parameter write tool with no output schema, the description covers the security model and explicitly states what comes back (metadata only), which is the key unknown for a secret-handling tool. Remaining gaps are secondary: overwrite behavior on repeat calls and any permission or confirmation requirements.

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 baseline is 3. The 'Args' block restates the schema descriptions for credential_type, value, and label almost verbatim without adding format constraints, allowed-value enforcement, or handling notes, so it adds no meaning beyond the structured fields.

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?

The description opens with a specific verb+resource pair ('Encrypt and store a credential') and enumerates the credential kinds covered, so the agent knows exactly what this tool does. It does not explicitly contrast itself with the closely related siblings list_credentials and retrieve_credential, which keeps it off 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus retrieve_credential/list_credentials, no prerequisites, and no guidance on what happens if a credential of the same type already exists (overwrite vs. duplicate). The only usage signal is implied by the verb 'store'.

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