Skip to main content
Glama

Create (or rename) a workspace's vault

create_vault

Creates a workspace secret vault or renames an existing one, defining the identifier code uses to reference secrets. Only the workspace owner can do this; renaming requires confirm=true.

Instructions

Creates the workspace's secret vault, or renames an existing one. The name is the IDENTIFIER block code uses: with name "MyVault", a secret "prodDb" is referenced as MyVault.prodDb. Do this once, then add secrets with set_vault_secret. Renaming an existing vault BREAKS code that references the old name, so it requires confirm=true. Only the workspace OWNER can.

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": {
      "workspaceId": "<workspaceId>",
      "name": "<name>"
    },
    "name": "create_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVault identifier used in block code, e.g. "MyVault". Letters/digits/underscore.
confirmNoRequired only when renaming an existing vault (creating a new one does not need it).
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the downstream breakage from renaming, the confirm=true guard, and the OWNER-only permission requirement. It still leaves open what happens if a vault already exists under that name and whether the call is idempotent, which matters for a create-or-rename 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?

Four sentences, each carrying distinct payload: the action, the identifier semantics, the sequencing, and the rename risk. The destructive warning is stated before the authorization note, so the highest-stakes information appears early rather than buried.

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 three-parameter mutation with no annotations and no output schema, the description covers permissions, the destructive rename path, the confirm guard, and the follow-up workflow. It would be complete with a note on existing-vault collision behavior and whether the created vault is returned.

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 67% and the schema already documents name and confirm, including the rename-only condition on confirm. The description adds the concrete MyVault.prodDb reference pattern, which clarifies what the identifier means in practice, but says nothing about workspaceId, leaving that parameter to the schema alone. This is baseline-plus, not a substantial gain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Creates the workspace's secret vault, or renames an existing one"), which covers both modes of the tool in one line. It separates itself from set_vault_secret by naming that sibling as the follow-up step, so an agent can distinguish the two without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit ordering rule ("Do this once, then add secrets with set_vault_secret") and a conditional for the rename path. What's absent is a when-not or an explicit condition identifying an existing vault (the name collision is left for the agent to infer) and guidance on whether re-running is safe.

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