Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Notes

keychain_get_notes
Read-only

Fetch item notes from your vault using a search term or exact ID. Notes remain hidden by default; enable reveal to view secret values unless NOREVEAL is active.

Instructions

Get item notes matched by bw get notes for a search term. Notes are treated as secret output here: value is null unless reveal=true and NOREVEAL is not active. Terms can be ambiguous, so prefer an exact item id when possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term or exact item id; exact ids avoid ambiguous bw lookups.
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. Dates show when Glama detected each change.

  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; exact ids avoid ambiguous bw lookups."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "const": "notes",
+          "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

A3.9/5.0
Behavior4/5

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

ReadOnlyHint is already present, and the description adds meaningful behavior beyond it: notes are treated as secret output, value is null unless reveal=true, and NOREVEAL can force redaction. This is valuable disclosure for an agent deciding whether secrets will be exposed.

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?

Three focused sentences, front-loaded with purpose, followed by important secret-handling nuance and a clear usage tip. Every sentence earns its place and nothing feels redundant.

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 tool with full schema coverage, an output schema, and readOnly annotation, the description is nearly complete. It covers purpose, secret behavior, and ambiguity guidance; only a named sibling alternative or explicit non-use condition is missing.

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%, so the baseline is 3. The description adds practical parameter meaning: exact ids avoid ambiguous bw lookups, and reveal=true can still be overridden by NOREVEAL. This goes beyond the schema's descriptions.

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?

Description states a specific verb+resource: 'Get item notes' with search-term matching. It is clear and distinct from the clustered get_* siblings because it targets notes, but it does not explicitly differentiate itself from those siblings.

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?

Provides practical context: terms can be ambiguous and exact item ids are preferred. However, it does not explicitly state when to use this tool versus alternatives such as keychain_get_item, nor when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icoretech/warden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server