Skip to main content
Glama
Sign In
DevVault MCP

DevVault MCP

by ConjureGanja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rotate a secret

rotateSecret

Rotate a secret's stored value without returning the plaintext, ensuring it never enters model context.

Instructions

Replace a secret's value. The value is never returned.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
valueYes
projectNodefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided. The description discloses that the value is never returned, which is important security context, but it does not mention behavior for non-existent secrets, permissions, or what response to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with no filler, but it omits parameter details and usage context, making it efficient yet under-specified.

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?

With 3 parameters and no output schema, the description lacks essential operational details like error conditions, success indicators, and when rotation is applicable compared to storeSecret.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description only mentions 'value' indirectly, with no explanation of 'name', 'project', or how they relate to the operation.

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 uses the specific verb 'Replace' and identifies the resource 'secret's value', clearly distinguishing from siblings like storeSecret (store) and deleteSecret (delete).

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

Usage Guidelines3/5

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

The description implies the tool is for changing an existing secret's value but does not explicitly state when to use it versus storeSecret or provide any prerequisites or exclusion criteria.

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

Deploy Server

Other Tools