Skip to main content
Glama

vault_list

List the keys stored in your pocket with their sizes and update times. Same arguments as vault_read, and the same as leaving the key out there.

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": {
      "vault_id": "<vault_id>",
      "secret": "<secret>"
    },
    "name": "vault_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
secretYesThe `secret` returned by vault_create, starting with `abp_`.
vault_idYesThe `vault_id` returned by vault_create. A UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / secret / description
      Added value: +"The `secret` returned by vault_create, starting with `abp_`."
    • addedInput schema / properties / vault_id / description
      Added value: +"The `vault_id` returned by vault_create. A UUID."
  2. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden: 'List' implies a read, but it never confirms this is non-mutating, whether it requires an unlocked vault or specific permissions, how keys are ordered, or whether output is paginated. The 'leaving the key out there' clause reads as an allusion to side effects without ever stating one.

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 first sentence is efficient and front-loaded, but the second is a low-value comparison that consumes half the text without conveying usable information. Brevity is good; the second sentence does not earn its place.

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?

With only two fully documented parameters and no output schema, the description usefully names the returned fields (sizes, update times), which compensates somewhat for the absent output schema. However, ordering, limits, and read-only semantics are unaddressed, leaving meaningful gaps for a listing tool.

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 both vault_id and secret are already documented, and 'Same arguments as vault_read' adds no new meaning. Baseline 3 applies since the schema does the heavy lifting.

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 the keys') plus the fields returned ('sizes and update times'), which is more than a restatement of the name. The metaphorical 'stored in your pocket' phrasing obscures that this operates on a vault, and it does not explicitly contrast with vault_read or vault_write.

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 choose this over vault_read or the other vault siblings, and no prerequisites beyond 'same arguments as vault_read'. The trailing clause 'the same as leaving the key out there' is cryptic and provides no actionable guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.