Skip to main content
Glama

Update run-time variables

wopee_update_variables
DestructiveIdempotent

Upsert run-time variables for a project or a specific analysis suite, adding or overwriting listed uppercase keys while preserving existing variables.

Instructions

Upsert the run-time variables (additionalVariables) that drive analysis/agent runs, at either level. level: PROJECT writes the project-level variables (the connected project); level: ANALYSIS writes a specific analysis suite's variables and requires suiteUuid. Merge semantics: keys in variables[] are added or overwritten, existing keys not listed are preserved. Keys must be uppercase (e.g. BASE_URL); the server re-sanitizes and drops invalid keys. Returns a confirmation on success.

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": {
      "level": "<level>",
      "variables": "<variables>"
    },
    "name": "wopee_update_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesWhich variable set to write. PROJECT writes the project-level variables (the connected project). ANALYSIS writes a specific analysis suite's variables and requires suiteUuid.
suiteUuidNoUUID of the analysis suite to write variables to. Required when level is ANALYSIS; ignored when level is PROJECT.
variablesYesVariables to upsert. Each needs an uppercase key (e.g. BASE_URL) and a non-empty value. Merge semantics: keys listed here are added or overwritten; existing keys not listed here are preserved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.39.4
    • changedInput schema / properties / level / description
      Previous value: -"Which variable set to write. PROJECT writes the project-level variables (uses WOPEE_PROJECT_UUID from the environment). ANALYSIS writes a specific analysis suite's variables and requires suiteUuid."New value: +"Which variable set to write. PROJECT writes the project-level variables (the connected project). ANALYSIS writes a specific analysis suite's variables and requires suiteUuid."
  2. Changed2 schema fields changedv1.32.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / variables / items / additionalProperties
      Removed value: -false
  3. Addedv1.29.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description earns credit beyond them by spelling out merge semantics (listed keys added or overwritten, unlisted keys preserved), the silent key-dropping behavior, and the success response shape. It doesn't cover auth requirements or whether suite-level and project-level sets interact, so not a 5.

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?

Front-loaded with the action and scope, then merge semantics, then the key constraint and return behavior — a sensible order. Slightly dense, and the level/suiteUuid explanations duplicate the input schema verbatim, which is wasted space.

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 3-parameter mutation with no output schema, the description covers scope, merge behavior, key validation, and confirms a confirmation is returned — enough for an agent to call it correctly. The remaining gap is permission/auth prerequisites for writing variables.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning not in the schema: that the server re-sanitizes and silently drops invalid keys rather than erroring, and it reiterates the uppercase key convention with an example. It restates suiteUuid/level semantics already documented in the schema, so some redundancy caps it at 4.

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?

Specific verb+resource: 'Upsert the run-time variables (additionalVariables)'. It also names the domain being affected (analysis/agent runs) and the two write targets. It stops short of naming wopee_fetch_variables as the read counterpart, so sibling differentiation is implicit rather than explicit.

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

Usage Guidelines4/5

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

Gives clear selection rules: level PROJECT writes project-level variables, level ANALYSIS writes a suite's variables 'and requires suiteUuid'. It doesn't state when-not to use this tool, or point the agent at wopee_fetch_variables for reads, so exclusions are absent but the positive routing is unambiguous.

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