keyshade-mcp

Official

Overview Schema Source Related Servers Discussions Admin

create_variable

Create a new variable for a project by specifying a name, project slug, and entries with environment slugs and values. Use this to manage configuration per environment.

Instructions

Creates a new variable 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": {
      "name": "<name>",
      "entries": "<entries>",
      "projectSlug": "<projectSlug>"
    },
    "name": "create_variable"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`note`	No
`entries`	Yes
`projectSlug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavior. Only states 'creates a new variable' without mentioning side effects, permissions, or idempotency. Minimal transparency.

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

Conciseness3/5

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

Single sentence, very concise. However, it sacrifices necessary detail; front-loading is fine but incomplete.

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

Completeness1/5

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

With 4 parameters, no output schema, and no annotations, this description is severely lacking. Doesn't explain the structure of 'entries' (environment-specific values) or that the variable is created in a project.

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

Parameters1/5

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

Schema has 0% description coverage and the description adds no meaning to parameters like 'name', 'note', 'entries', or 'projectSlug'. Agent must infer their purpose from names alone.

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?

The description specifies the verb 'creates' and resource 'variable in a project' clearly. It distinguishes from sibling tools like update_variable or delete_variable, but could be more specific about the type of variable.

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 over alternatives like create_secret or update_variable. Missing context about prerequisites or constraints.

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