Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_tap_secrets

Lists existing tap secret names to help you reuse suitable credentials before creating a new tap secret. Check first to avoid duplicates and request credentials only when no match exists.

Instructions

List the names of tap secrets that already exist (secrets tagged _type=tap — both agent-created and human-owned ones surfaced via the UI's Tap Secrets section). ALWAYS call this before create_tap_secret: if a suitable secret already exists, prefer reusing it by passing its name as secret_name to create_tap. Only ask the user to provide credentials when no existing secret covers the need.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it discloses two non-obvious traits: that only names are returned (not secret values) and that the result set includes both agent-created and human-owned secrets. It stops short of stating ordering, empty-result behavior, or any permission/rate-limit considerations, which for a zero-parameter read tool are minor but not fully covered.

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?

The purpose is front-loaded in the first clause, followed by scope and then prescriptive workflow guidance; nothing is redundant. The parenthetical about agent-created versus human-owned secrets is slightly wordy but earns its place by clarifying scope.

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?

There is no output schema, and the description compensates by stating that the tool returns secret names, which is exactly what the caller needs to know before reusing one. Given zero parameters and simple read semantics, the only remaining gaps are result ordering and behavior when no secrets exist.

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?

There are zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The mention that a returned secret can be reused by passing its name as secret_name to create_tap usefully connects this tool's output to another tool's parameter.

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 a specific verb and resource ("List the names of tap secrets that already exist") and immediately narrows scope to secrets tagged _type=tap, including the note that both agent-created and human-owned secrets are covered. That scope definition, plus the contrast with the UI's Tap Secrets section, makes it distinguishable from list_platform_secrets and gives a precise picture of what is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit and prescriptive: "ALWAYS call this before create_tap_secret" gives the trigger, reusing via secret_name on create_tap gives the preferred alternative, and "only ask the user to provide credentials when no existing secret covers the need" gives the when-not case. It routes the agent through the correct create_tap_secret/create_tap workflow rather than leaving sequencing to inference.

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