Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Update Var

updateVar
Destructive

Change an environment variable’s value, secret status, or name; renaming preserves the stored value so secrets need not be resent, and duplicate names are rejected.

Instructions

Change a variable's value, whether it is secret, or its name. A new name keeps the value, so a secret can be renamed without sending it again; a name another variable has is refused.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>",
      "varId": "<varId>"
    },
    "name": "updateVar"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
varIdYes
regionNo
appSlugYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.0
    • addedInput schema / properties / requestBody / properties / key
      Added value: +{
      +  "maxLength": 80,
      +  "pattern": "^[A-Z_][A-Z0-9_]*$",
      +  "type": "string"
      +}
  2. First observedv0.5.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation surface is known. The description adds genuinely new behavior: a rename preserves the existing value (avoiding resending a secret) and a duplicate key is rejected. It still omits whether an update triggers a redeploy/restart and whether unspecified fields are preserved or cleared.

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?

Two dense sentences with no filler, and the primary action is front-loaded. The phrasing 'whether it is secret, or its name' is slightly compressed to the point of ambiguity about which fields are optional.

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

Completeness4/5

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

For a destructive mutation with no output schema, the description covers the key semantics and one error case. Given the schema's low coverage it could say more about the identification parameters and about side effects on running apps, so it falls short of fully complete.

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 description coverage is only 17% across six parameters with a nested requestBody, so the description must compensate and it partly does by mapping 'value', 'secret', and 'name' to the requestBody fields. The contextual parameters (workspaceSlug, appSlug, varId, env, region) get no explanation in either place, and 'name'/'key' naming is not reconciled.

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?

States a specific verb (change) and enumerates the mutable fields of a variable: value, secret flag, and name. It is clearly distinguishable from createVar/deleteVar/listVars by implication, though it never names a sibling explicitly.

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?

Usage is implied through the rename scenario ('a secret can be renamed without sending it again'), which tells the agent one good reason to pick this over a delete+create. There is no explicit when-not guidance or routing to siblings such as createVar or revealVar.

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