Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_tap_secret_fields

Use after listing tap secrets to retrieve only field names and confirm the keys your tap script needs; secret values are never returned.

Instructions

Return the FIELD NAMES (keys only — never values) of an existing tap secret. Use this after list_tap_secrets to verify a candidate secret has the keys your tap script will need (e.g. API_KEY, USER_AGENT). Secret values are intentionally NOT returned and are never visible to the agent.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTap secret name (from list_tap_secrets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 burden itself and does well: it twice declares that secret values are never returned or visible to the agent, which is the key safety expectation for this call. It omits other behavior an agent might want, such as what happens when the named secret does not exist or whether access is permission-gated.

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?

The keys-only constraint is front-loaded and emphasized, followed by usage sequencing and a brief rationale. All three sentences earn their place with no redundancy.

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 one-parameter read tool with no output schema, the description covers purpose, timing, and the critical non-disclosure of values. The exact return shape (for example, a list versus a keyed object of field names) is left implicit, a minor gap.

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 'name' parameter is already documented in the schema as coming from list_tap_secrets. The description adds no syntax, format, or validation detail beyond that, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Return the FIELD NAMES ... of an existing tap secret') and immediately bounds the scope to keys only, never values. It is clearly distinguishable from list_tap_secrets (which enumerates secrets) and from any value-returning operation.

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?

It gives explicit sequencing guidance ('Use this after list_tap_secrets') and a concrete motive ('verify a candidate secret has the keys your tap script will need'). It does not address when not to use it, such as preferring get_platform_secret_fields for platform-scoped secrets, so it falls short of a full 5.

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