Skip to main content
Glama

vault_read

Read one value from your pocket by key, or omit the key to list every key with its size. Only your secret opens the pocket.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOptional; omit to list all keys.
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

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the key behavioral fact that the secret is the authorization mechanism ('Only your secret opens the pocket') and that listing mode returns key names with sizes. It says nothing about what happens with an invalid secret, whether the value is returned as a raw string or encoded, or any size limits — meaningful gaps for an unannotated 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 short sentences, front-loaded with the primary read operation before the alternate list mode. No filler; even the metaphor is doing work by conveying the authorization requirement. Nothing could be cut 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?

For a three-parameter, no-annotation, no-output-schema tool, the description covers purpose, the optional-key branch, and the auth requirement. It leaves the return shape of the value itself unspecified — an agent cannot tell whether it gets a plain string, a structured envelope, or an error object on failure. Adequate but not complete.

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 coverage is 100%, so all three parameters are already documented, including the optional key and the abp_ prefix convention for secret. The description restates the key-omission behavior already present in the schema, adding no new syntax, format, or constraint detail. Baseline 3 is right when 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?

The description names a specific verb (read) and resource (one value from your pocket by key) and adds a second distinct mode (list all keys with sizes when the key is omitted). The metaphor 'pocket' is slightly informal for what the name calls a vault, but the operation is unambiguous. It does not distinguish itself from the sibling vault_list, which an agent might reasonably confuse with the list mode described here.

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?

It gives one clear conditional instruction — omit the key to list all keys — which is real usage guidance for the primary branch. It offers no guidance on when to choose this over vault_list for enumeration, nor any prerequisites or error conditions. Usage is implied rather than fully framed.

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.