revealVarDecrypt and retrieve the plaintext value of a stored secret variable for a specified app and environment, enabling secure access to configuration secrets.
Reveal the decrypted value of a secret variable
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | ||
| varId | Yes | ||
| region | No | ||
| appSlug | Yes | ||
| workspaceSlug | Yes |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint: true and destructiveHint: false annotations already communicate the safety profile. The description adds the useful behavioral detail that decryption occurs, but does not disclose additional context such as security implications of revealing secrets or any rate limits or auth requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, highly concise, and front-loaded with the key action verb 'Reveal' at the start. No unnecessary words or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is security-sensitive (revealing secrets) and has five parameters with no schema descriptions, yet the description provides no context about return value shape, security warnings, or parameter relationships. The description is too minimal to fully guide an agent given the tool's complexity and sensitivity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% (no parameter descriptions in the schema), which is below the 50% threshold requiring compensation from the description. The description does not mention any of the five parameters (workspaceSlug, appSlug, varId, env, region), leaving the agent with no semantic guidance for parameter usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Reveal') and resource ('decrypted value of a secret variable'), clearly distinguishing it from sibling tools like listVars (which presumably lists variable metadata without decrypting values), createVar, updateVar, and deleteVar.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'decrypted value' implies the tool is used when the actual secret value is needed, contrasting with listVars which likely returns metadata only. However, it does not explicitly name an alternative sibling tool or state conditions for choosing this tool over others.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.