Skip to main content
Glama

create_secret_key

create_secret_key

Create a new active secret key for the connected test app and return its ID and metadata only. Never returns the secret value. Ask the user to view it in the TalkJS dashboard or manually run talkjs secret-keys get <id> in their terminal. Creates a new key on every call; at most 10 keys are allowed. Does not change webhook selection.

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": "create_secret_key"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag a non-read-only, non-idempotent, non-destructive operation, and the description adds the material consequences: the secret value is never returned, a new key is minted on every call (so retries duplicate), a hard cap of 10 keys applies, and webhook selection is untouched. Those are exactly the facts an agent needs before invoking a write.

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?

Purpose is front-loaded in the first clause, followed by the return-value caveat, the remediation path, and the quota constraint in descending order of importance. Every sentence carries a distinct, actionable fact with no 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?

There is no output schema, and the description compensates by explaining exactly what comes back (ID and metadata only, never the secret). With no parameters to document and annotations covering the safety profile, nothing an agent needs to call this correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies no arguments are needed and that the target app is implicit ("the connected test app"). Nothing further about parameters is required.

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?

Opens with a specific verb and resource ("Create a new active secret key") and narrows the scope to "the connected test app," which distinguishes it from the read/delete/update siblings. An agent can tell this is the provisioning tool without opening the schema.

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?

Gives clear operational context: this is the creation path, and it points the agent to a follow-up action (dashboard or `talkjs secret-keys get <id>`) rather than a retrieval tool. It never explicitly names a sibling like get_secret_key or list_secret_keys as an alternative, so the routing guidance is strong but not exhaustive.

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