Skip to main content
Glama

Runtime-permitted Vault values for this credential

vault_runtime
Read-only

Key/value map of Vault items marked runtime, merged personal → Space → API key.

GET /api/v1/vault/runtime

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId.

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

Input Schema

NameRequiredDescriptionDefault
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / targetSpaceId
      Added value: +{
      +  "description": "Busabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-structured behavior: items are filtered to those marked `runtime`, and precedence is personal → Space → API key, which tells the agent how conflicting values resolve. It stops short of saying whether values are returned masked or how empty scopes behave.

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?

Front-loaded with the return shape and merge order, then the endpoint, then the conditional guidance — good ordering, no filler prose. Minor waste: the raw GET path line and the space-selection sentence duplicating the schema description nearly verbatim.

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?

With no output schema, the description does its job by naming the return type (key/value map) and its scope. For a single-optional-parameter read tool with read-only annotations, an agent has enough to call it correctly; only error/empty-case behavior is unaddressed.

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% and the targetSpaceId description already spells out the auth_verify / ask-the-user flow, so the description's restatement adds no new semantics. Baseline 3 applies since the schema carries the full parameter burden.

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 precisely what is returned: a key/value map of Vault items marked `runtime`, with the merge precedence personal → Space → API key. An agent knows this is a runtime-scoped, secrets-adjacent lookup, not a general Vault listing, and no sibling tool in the list overlaps with it.

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?

Gives a concrete conditional flow: for multi-space accounts, call auth_verify, ask the user which space, then pass targetSpaceId. That is real usage guidance for the only branching decision this tool has. It does not name when *not* to use it, but there is no competing sibling to exclude.

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.