Skip to main content
Glama

vault_write

Save one named value in your pocket. Writing the same key again replaces it, so this is also how you update a note.

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>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "vault_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesName of this value inside the pocket, e.g. 'results'.
valueYesText or JSON, as a string.
secretYesThe `secret` returned by vault_create, starting with `abp_`. Shown once; it cannot be recovered.
vault_idYesThe `vault_id` returned by vault_create, e.g. '409dffac-b97a-4ed5-8844-f838e2f21ee8'. A UUID, not the label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / key / description
      Added value: +"Name of this value inside the pocket, e.g. 'results'."
    • addedInput schema / properties / secret / description
      Added value: +"The `secret` returned by vault_create, starting with `abp_`. Shown once; it cannot be recovered."
    • addedInput schema / properties / vault_id / description
      Added value: +"The `vault_id` returned by vault_create, e.g. '409dffac-b97a-4ed5-8844-f838e2f21ee8'. A UUID, not the label."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose the critical overwrite/upsert semantic so an agent knows existing values under the same key are destroyed. It does not cover whether other keys are preserved, what the call returns, error behavior, or size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and immediately followed by the replacement behavior. No wasted wording, though the 'pocket' metaphor trades a little precision for tone.

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 four-parameter write tool with fully documented parameters, the description covers the essential behavior an agent must know before calling it, namely overwrite semantics. Return values and failure modes are the remaining gaps, but no output schema exists so that is a modest omission.

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, and the description adds real meaning beyond the schema by clarifying that `key` identifies a slot that can be overwritten rather than appended. That upsert framing is not visible in the schema itself.

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 states a specific verb and resource: save one named value, and explicitly notes that re-writing a key replaces it. The only weakness is the metaphor 'in your pocket' instead of naming the vault as the resource, but the tool name plus schema make the target unambiguous.

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 implies the update path by saying writing the same key again replaces the value, which tells an agent this is both create and update. It gives no explicit guidance on when to prefer vault_read or vault_list instead, and no prerequisite note about needing a secret from vault_create.

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.