Brainz

Create a vault

create_vault

Create a new, empty vault owned by you and add it to this connection. Returns the new vault and the vaults this connection can now use. Once a connection covers more than one vault, every vault tool takes a vault argument (a slug or id) and list_vaults lists the vaults. Each account has a vault limit and an hourly creation limit.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	The new vault's display name.
`slug`	No	Optional slug (lowercase letters, digits, dashes). Derived from `name` when omitted; must not already be used by one of your vaults.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only cover the read/write and open-world profile; the description adds real context beyond them: the return payload (new vault plus the connection's usable vaults), the account vault limit and an hourly creation limit. It does not say what happens on slug collision or limit breach, which keeps it from a 5.

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?

Three sentences, front-loaded with the action and the return value, then the multi-vault consequence and limits. The `vault`-argument sentence is cross-cutting context rather than this tool's own behavior, so a small amount of text is not strictly self-serving.

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?

Covers what is created, what is returned (in lieu of an output schema), and the quota/rate-limit constraints an agent should anticipate. An agent has enough to call it correctly; only error/degraded-case behavior is unstated.

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 `name` and `slug` semantics (derivation rule, lowercase/digit/dash format, uniqueness) are already fully documented in the schema. The description adds no field-level detail, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ('Create a new, empty vault') plus ownership and the side effect of attaching it to the current connection. No sibling creates vaults, so it is unambiguous among the listed tools.

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?

Implies when to use it (bootstrap a new vault owned by the caller) and describes the resulting switch to multi-vault mode where every vault tool needs a `vault` argument. It does not name a when-not condition, but there is no competing sibling tool to route away from.

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

All Brainz tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?