Skip to main content
Glama

update_secret

Idempotent

Rotate an existing workspace secret. Fails if the name is missing. The value is never returned. Use when replacing a credential that list_secrets already shows.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
valueYesNew secret value. Never echoed in the result.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses two real behaviors: failure when the name is missing, and that the value is never returned. It does not say whether existing consumers of the secret are invalidated after rotation, which is the main remaining unknown for a mutate operation.

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 the failure condition, then the return-value constraint, then routing guidance. No filler.

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?

With no output schema, the description correctly closes the loop by stating the value is never returned, and it covers the required-parameter failure mode. Only the undocumented 'description' parameter and post-rotation effects keep it from full completeness.

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 only 33%, so the description must compensate. It does add meaning for 'name' (must exist, else failure) and 'value' (never echoed), but the third parameter 'description' is documented in neither schema nor description, leaving a genuine 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 description states a specific verb and resource - 'Rotate an existing workspace secret' - and the word 'rotate' clarifies this is replacement of an existing credential rather than creation. It is immediately distinguishable from create_secret and list_secrets without opening any 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?

It gives an explicit usage trigger: 'Use when replacing a credential that list_secrets already shows,' naming the sibling whose output precedes this call. There is no explicit when-not clause (e.g., use create_secret for new names), but the rotation framing implies 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