Skip to main content
Glama

List a workspace's vault secrets (names only)

list_vault_secrets
Read-only

Lists a workspace's vault and secret names, with kind and database provider metadata but no values, so you can reference connections as . in Process blocks.

Instructions

Lists the vault name and secret names available to a workspace's Process blocks — NAMES and metadata (kind, db provider) only, never values. Reference a connection in code as ., e.g. sql.query(MyVault.prodDb, ...). If it's empty, create the vault with create_vault and add secrets with set_vault_secret — no UI step needed.

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

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 the description adds meaningful behavior beyond that: the response contains names and metadata but never secret values, and it explains how to reference the returned connection in code as <vaultName>.<secretName>. It omits pagination, ordering, and what happens for an invalid or inaccessible workspaceId.

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?

One compact paragraph that front-loads the names-only constraint, then the reference syntax with a concrete example, then the empty-state remedy. The code example earns its place; there is no filler, though the sentence is dense.

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 read-only, single-parameter listing tool with no output schema, the definition covers scope, returned fields (name plus kind and db provider), the values-excluded guarantee, and the empty-result path. Only parameter format and result ordering remain unspecified.

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 0% for the single workspaceId parameter, so the description must carry the load. It conveys that secrets are scoped to a workspace, but never clarifies that workspaceId is a numeric identifier or how to obtain one, so the only parameter remains partially under-explained.

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?

Names a specific verb and resource ('Lists the vault name and secret names available to a workspace'), and immediately bounds the scope with 'NAMES and metadata (kind, db provider) only, never values', which separates it from create_vault and set_vault_secret by behavior rather than by name alone.

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 clear context of use (discovering what a workspace's Process blocks can reference) and an explicit fallback path: if the result is empty, call create_vault then set_vault_secret. It stops short of an explicit 'when not to use this' or naming an alternative listing tool, so it is strong but not complete routing guidance.

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