Skip to main content
Glama

vault_create

Create a private pocket for yourself and get a secret. Keep the secret: it is the only way back, and it cannot be recovered. The pocket holds small notes and results — up to 1 MiB total — for six months.

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": "vault_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOptional short name so you recognise the pocket later.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present the description carries the full burden and does real work: it discloses that the call yields an unrecoverable secret, that storage is capped at 1 MiB total, and that contents expire after six months. It omits whether repeated calls create multiple independent pockets and how the secret is surfaced in the response.

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?

Three short sentences, front-loaded with the action and the critical warning, then capacity and lifetime. Nothing is padding and every sentence carries distinct information.

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 zero-required-parameter creation tool with no output schema and no annotations, the description covers the essential unknowns: what you get back, that it is unrecoverable, and the capacity/retention envelope. Only the shape of the return value and multi-call behavior are left implicit.

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?

One optional parameter at 100% schema coverage, and the description never mentions the 'label' parameter at all. The schema already documents it fully, so the baseline of 3 applies with no added meaning from the description.

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?

Specific verb 'create' plus a concrete resource ('private pocket') and the immediate outcome ('get a secret'). It is clearly separable from vault_read/vault_write/vault_delete by implication of the name, but the description itself never names a sibling or contrast case.

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?

Gives strong post-call guidance — keep the secret, it is the only way back, it cannot be recovered — which effectively tells the agent to persist the return value. It does not, however, say when to prefer creating a new vault versus reusing an existing one, nor point to vault_list/vault_write as next steps.

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.