keyshade-mcp

Official

by keyshade-xyz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

update_secret

Update a secret's name, note, environment values, or rotation interval directly.

Instructions

Updates a secret in a project

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": {
      "secretSlug": "<secretSlug>"
    },
    "name": "update_secret"
  }
}

Input Schema

Name	Required	Description
`name`	No	New secret name
`note`	No	New secret note
`entries`	No	New secret values for environments
`secretSlug`	Yes	Secret slug to update
`rotateAfter`	No	Rotation interval (24, 168, 720, 8760, never)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It only says 'updates', implying mutation, but does not clarify partial updates, side effects, or permissions needed. This is insufficient for a mutation 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?

Extremely concise, one sentence that is front-loaded with the key action. No unnecessary words.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 5 parameters and no output schema, the description is too minimal. It does not explain partial update behavior, return value, or error conditions, leaving gaps for an agent.

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% with parameter descriptions, so the schema already documents the parameters. The description adds no additional meaning beyond the schema, baseline score 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?

Description clearly states it updates a secret in a project, which distinguishes from create_secret and delete_secret. However, it could be more specific about what aspects can be updated (name, note, values, rotation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like deleting and recreating a secret. No prerequisites or context provided.

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