Skip to main content
Glama

list_secrets

Read-onlyIdempotent

Retrieves tenant secret metadata and returns secret names usable as secret_ref, without exposing credential values.

Instructions

List tenant secret metadata without exposing credential values. Use each name as secret_ref where supported.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: results are metadata only and credential values are never exposed, which prevents an agent from expecting secret material. It stops short of describing ordering, pagination, or metadata fields.

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?

Two short sentences with no filler, and the most important constraint (no credential values) is stated up front. The phrase 'where supported' is slightly vague but does not cost much space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry the burden of describing return content; it does so partially by stating that names and metadata come back. It omits what metadata fields are included and whether results are paginated, which leaves a modest gap for an agent planning follow-up calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to clarify. The description correctly implies a whole-tenant listing with no filtering arguments, consistent with the empty schema.

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?

The description gives a specific verb and resource ('List tenant secret metadata') plus an important scope qualifier ('without exposing credential values'), so an agent knows exactly what comes back. It does not explicitly contrast with near-neighbors such as list_api_keys or list_integration_grants, so it falls short of full sibling differentiation.

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?

The second sentence, 'Use each name as secret_ref where supported,' tells the agent what to do with the output, which implies when to call it. However, there is no explicit statement of when to prefer this over other listing tools, nor any prerequisite or exclusion guidance.

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

Deploy Server

Other Tools