Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_platform_secret_fields

Returns only a platform secret's field names so you can verify it has the keys a destination config requires; values are never exposed.

Instructions

Return the FIELD NAMES (keys only — never values) of an existing platform secret. Use this after list_platform_secrets to verify a candidate secret has the keys a destination config requires (e.g. an S3 credentialsSecret must contain accessKey, secretKey, region). Secret values are intentionally NOT returned. If the named secret is tap-tagged, this tool refuses — use get_tap_secret_fields for those.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPlatform secret name (from list_platform_secrets).

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?

No annotations exist, so the description carries the full burden, and it does disclose the two most important behaviors: only key names are returned (never values) and the tool refuses on tap-tagged secrets. It does not say what happens if the named secret does not exist or what error/lookup-failure looks like, which leaves a minor gap for a tool with zero annotation coverage.

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?

Three sentences, each doing distinct work: what is returned, when to use it with an example, and the refusal/alternative path. The keys-only constraint is front-loaded where it will be read first, and nothing is redundant.

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

Completeness5/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 everything an agent needs: the shape of the return value (key names only), the intended lookup flow, and the case where the call will not work. Little is left to inference.

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?

There is a single required parameter with 100% schema description coverage, and the schema already tells the agent the name comes from list_platform_secrets. The description reinforces that provenance but adds no format or naming-convention detail beyond the schema, so the baseline of 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 opens with a specific verb and resource ('Return the FIELD NAMES ... of an existing platform secret') and immediately narrows the scope with 'keys only — never values'. It also names the sibling it is not (get_tap_secret_fields), so an agent can distinguish it without opening either schema.

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?

It gives an explicit workflow context ('Use this after list_platform_secrets to verify a candidate secret has the keys a destination config requires') with a concrete example of the S3 credentialsSecret case. It also states an exclusion and the correct alternative: tap-tagged secrets cause a refusal, so use get_tap_secret_fields instead.

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