Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Password

keychain_get_password
Read-only

Retrieve a stored login password from the vault by search term or item ID, with optional reveal control and redaction safeguards.

Instructions

Get a login password by search term (bw get password). The value is null unless reveal=true, and NOREVEAL or KEYCHAIN_NOREVEAL can still force redaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term or exact item id used for bw get password.
revealNoWhether secret values are returned; default false and can be forced false by NOREVEAL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.35
    • removedOutput schema / properties / result / properties / value / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / result / properties / value / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed3 schema fields changedv0.2.19
    • addedInput schema / properties / reveal / description
      Added value: +"Whether secret values are returned; default false and can be forced false by NOREVEAL."
    • addedInput schema / properties / term / description
      Added value: +"Search term or exact item id used for bw get password."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "const": "password",
+          "type": "string"
+        },
+        "revealed": {
+          "type": "boolean"
+        },
+        "value": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "kind",
+        "value",
+        "revealed"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  3. Addedv0.1.20

TDQS

A4.4/5.0
Behavior5/5

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

The description discloses important runtime behavior beyond the readOnlyHint annotation: the value is null unless reveal=true, and NOREVEAL/KEYCHAIN_NOREVEAL can force redaction. This is essential, non-obvious behavioral context for a secret-retrieval tool.

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 tight sentences with no filler. The core action is front-loaded, and the critical caveat about reveal/redaction is included without unnecessary detail.

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 simple two-parameter getter with an output schema and readOnlyHint annotation, the description is nearly complete. The only gap is explicit guidance on when to choose this over closely related sibling getters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents both parameters well. The description adds value by clarifying the null-result behavior when reveal is false, which goes slightly beyond the schema's phrasing.

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

Purpose5/5

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

The description states a specific verb and resource: 'Get a login password by search term', and references the underlying 'bw get password' command. This clearly distinguishes it from sibling getters like keychain_get_password_history or keychain_get_item.

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 description implies use for retrieving a login password via a search term or ID, but it does not explicitly state when to prefer this over alternatives such as keychain_get_item or keychain_get_password_history. Usage context is present but left to inference.

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