keyshade-mcp

Official

by keyshade-xyz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

delete_variable_environment_value

Delete the environment-specific value of a variable to update configuration per environment.

Instructions

Deletes an environment-specific value of a variable

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": {
      "variableSlug": "<variableSlug>",
      "environmentSlug": "<environmentSlug>"
    },
    "name": "delete_variable_environment_value"
  }
}

Input Schema

Name	Required	Description	Default
`variableSlug`	Yes
`environmentSlug`	Yes

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?

With no annotations, the description carries full burden but only states the action. It does not disclose behavior such as error conditions, permission requirements, or side effects (e.g., what happens if the variable or environment does not exist).

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 a single, efficient sentence with no wasted words. However, it could be slightly more informative without losing conciseness.

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?

Given no output schema and no annotations, the description is insufficient. It does not explain return values, error handling, or any side effects, leaving the agent underinformed for a destructive operation.

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 coverage is 0%, so the description must compensate but fails to define the parameters beyond their names. The property names are somewhat self-explanatory, but no additional semantics like format or constraints are provided.

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 clearly states the action (deletes) and the resource (environment-specific value of a variable). It effectively distinguishes from sibling tools such as delete_variable (deletes entire variable) and delete_secret_environment_value (similar but for secrets).

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 is provided on when to use this tool versus alternatives, prerequisites, or context. The description does not mention that it only removes the value for a specific environment, not the variable itself.

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