Skip to main content
Glama

list_secrets

Retrieves the names of a project's secrets, including who set each and when, without exposing secret values. Use it to audit ownership and timing while keeping values hidden.

Instructions

The names of a project's secrets (TR-775): who set each and when, never a value. To use them, run the command that needs them as tares factory with-secrets -- <command>, which sets them as environment variables for that command only. Never print a secret, write it to a file, or pass it on a command line. Only the project's members see this list.

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

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares the read-only, value-free nature of the result, states the access-control boundary ('Only the project's members see this list'), and warns against printing, persisting, or putting secrets on a command line. That is substantive behavioral context an agent could not infer from the schema.

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?

Four sentences, front-loaded with the return semantics, then the safe-usage path, then the prohibition, then the access rule. Each sentence earns its place; the '(TR-775)' ticket reference is minor noise.

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?

An output schema exists, so return shape need not be re-explained, and the description covers purpose, safety, and access. The remaining gap is argument format and any failure/permission-error behavior, which is small for a one-parameter list tool.

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 0% for the single `project` parameter, so the description must compensate. It establishes that the argument scopes to a project and that membership governs visibility, but never says whether `project` is a name, slug, or ID — the most likely source of a failed call.

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: secret names with who set each and when, and explicitly 'never a value'. That negative scope is the single most important distinction for this resource, and it is stated up front.

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?

Explains the follow-on path clearly — run the command as `tares factory with-secrets -- <command>` to get values as env vars for that command only — which is the real 'what to do next' guidance. It does not explicitly compare against alternatives, but no sibling in the provided list competes for this job.

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