Skip to main content
Glama

list_secrets

Discover which API-key secrets you can use by listing names, providers, and applicable policies, with optional substring filtering—without exposing secret values.

Instructions

List the secrets you may use, with their provider and the policy that applies to you. Never returns values.

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
filterNosubstring to match names, providers or tags

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose a genuinely useful safety trait — "Never returns values" — so an agent knows no secret material leaks through this call. However, it says nothing about permissions required, pagination, or whether results are filtered by the caller's identity beyond "you may use."

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?

Two compact sentences with zero filler, front-loading what is listed and its scope, then the key safety fact. Nothing could be removed without losing 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 simple single-optional-parameter read tool with no output schema, the description covers what is returned (provider and applicable policy) and the key guarantee (no values). Only the caller workflow and any pagination behavior are 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 single optional filter parameter is fully documented in the schema as a substring match across names, providers, or tags. The description adds no meaning beyond that, 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the secrets") plus the scoping constraint ("you may use") and the fields returned (provider, applicable policy). An agent can distinguish this read-oriented listing from siblings like call_api or request_access without opening the schema, though it never names an alternative explicitly.

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?

Usage is implied — call this to discover which secrets are available to you — but there is no explicit when-to-use versus when-not, no mention of what to do next (e.g. use call_api to invoke one), and no prerequisites stated. Adequate but leaves the agent to infer the workflow.

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