Skip to main content
Glama

get_secret_key

get_secret_key
Read-onlyIdempotent

Get a secret key's ID and metadata for the connected test app. Never returns the secret value. To view it, ask the user to open the key in the TalkJS dashboard or manually run talkjs secret-keys get <id> in their terminal.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe full 12-character ID returned by list_secret_keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the disclosure that the secret value is never returned. This prevents an agent from calling it repeatedly hoping to retrieve the credential, and the fallback instructions tell it what to do instead. It doesn't cover error behavior for an invalid ID, which keeps it below a 5.

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 short sentences, all front-loaded: what it returns, what it does not return, and what to do instead. Nothing is redundant with the title or restated for filler.

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 single-parameter read-only tool with full annotation coverage and no output schema, the description covers everything an agent needs: what comes back, what doesn't, and the manual alternative. No material gap remains.

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%; the single `id` parameter is fully documented in the schema, including its 12-character format and its origin from list_secret_keys. The description adds no further semantic detail about the parameter, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('Get a secret key's ID and metadata') and scopes it to 'the connected test app,' then immediately defines the boundary ('Never returns the secret value'). It is distinguishable from a mutation sibling like delete_secret_key, though it does not explicitly contrast with list_secret_keys beyond the singular 'a secret key'.

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 clearly defines what to do when the goal is obtaining the secret value itself: ask the user to open the key in the TalkJS dashboard or run `talkjs secret-keys get <id>` in a terminal. That is a concrete redirection rather than vague advice, but it gives no explicit guidance on when to prefer this over list_secret_keys.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources