Skip to main content
Glama
Sign In
aarifmms/keyblind

aarifmms/keyblind

by aarifmms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_secrets

Lists the names of secrets stored in the encrypted vault without revealing any secret values, so you can discover available credentials before requesting resolution.

Instructions

List all stored secret names (names only — values are never revealed in this listing).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault
expNoExpiry epoch seconds bound into the signature (required with agentId)
nonceNoSingle-use nonce bound into the signature (required with agentId)
tokenNoOrg-issued short-lived access token (alternative to agentId)
agentIdNoAgent ID for signed, scope-enforced access (optional)
signatureNoEd25519 signature over 'read:*:<nonce>:<exp>' in base64 (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.9.2
    • addedInput schema / properties / agentId
      Added value: +{
+  "description": "Agent ID for signed, scope-enforced access (optional)",
+  "type": "string"
+}
    • addedInput schema / properties / exp
      Added value: +{
+  "description": "Expiry epoch seconds bound into the signature (required with agentId)",
+  "type": "number"
+}
    • addedInput schema / properties / nonce
      Added value: +{
+  "description": "Single-use nonce bound into the signature (required with agentId)",
+  "type": "string"
+}
    • addedInput schema / properties / signature
      Added value: +{
+  "description": "Ed25519 signature over 'read:*:<nonce>:<exp>' in base64 (optional)",
+  "type": "string"
+}
    • addedInput schema / properties / token
      Added value: +{
+  "description": "Org-issued short-lived access token (alternative to agentId)",
+  "type": "string"
+}
  2. First observedv0.1.4

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose one genuinely valuable trait — that values are never returned — but says nothing about the auth model (token vs. signed agentId request with nonce/exp/signature), which is the dominant complexity of this 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?

A single tight sentence with the scope constraint front-loaded and no filler. Nothing could be removed without losing information.

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?

Adequate for a simple read-only listing, and the names-only constraint is the key fact. But with no annotations and no output schema, leaving the authentication requirements entirely to the schema makes the definition thinner than ideal for a tool with five credential parameters.

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?

All five parameters have schema descriptions (100% coverage), so the schema already documents them. The description adds no additional meaning about how exp/nonce/signature must be paired with agentId or when token is the preferred path, so it stays at baseline.

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 specific verb and resource ('List all stored secret names') and adds a decisive scope qualifier: names only, values never revealed. That distinguishes it from value-retrieving siblings like resolve_secret, though it never names them explicitly.

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?

No when-to-use guidance and no mention of alternatives such as resolve_secret or audit_log, even though those are the obvious adjacent tools. The 'names only' note implies it's for discovery, but the agent must infer that.

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