Skip to main content
Glama

create_secret

Store a new workspace secret (UPPER_SNAKE_CASE name). Fails if the name already exists; use update_secret to rotate. The value is never returned. Use when a playbook or tool needs a new API key or credential the vault does not already hold.

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>",
      "value": "<value>"
    },
    "name": "create_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUPPER_SNAKE_CASE name, e.g. STRIPE_SECRET_KEY
valueYesSecret value. Never echoed in the result.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description need only add nuance; it does so by disclosing the name-collision failure mode and that the value is never returned or echoed in the result. It does not cover required permissions or scope of visibility (who in the workspace can read it), which leaves a small behavioral gap for a credential-writing tool.

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?

Four short sentences, front-loaded with the action, then failure behavior, then confidentiality, then usage context. Nothing is redundant with the title or schema, and each sentence carries distinct information.

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 simple three-parameter write tool with no output schema and annotations covering the safety profile, the description covers purpose, failure mode, confidentiality, and routing to update_secret. The only shortfall is the undocumented optional 'description' parameter.

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?

At 67% schema coverage, the schema documents name (UPPER_SNAKE_CASE example) and value (never echoed); the description reinforces the naming format and the non-return of the value. However, the optional 'description' parameter has no documentation in either schema or description, so the description does not fully compensate for the coverage gap.

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 definition leads with a specific verb and resource ("Store a new workspace secret") and immediately adds a scoping constraint (UPPER_SNAKE_CASE name). It also names the sibling that handles the adjacent case (update_secret), so the agent can distinguish create from rotate without opening schemas.

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 states exactly when to use it ("when a playbook or tool needs a new API key or credential the vault does not already hold") and when not to (name already exists → use update_secret to rotate). The alternative is named explicitly with the condition that selects it.

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