Skip to main content
Glama

Fetch run-time variables

wopee_fetch_variables
Read-onlyIdempotent

Reads run-time variables at project or analysis level for analysis and agent runs, returning key-value entries with secret values masked. Use to inspect configuration driving test execution.

Instructions

Read the run-time variables (additionalVariables) that drive analysis/agent runs, at either level. level: PROJECT returns the project-level variables (the connected project); level: ANALYSIS returns a specific analysis suite's variables and requires suiteUuid, including the analysis' own TESTING_USERNAME, TESTING_PASSWORD, WOPEE_DEVICE and WOPEE_BROWSER when its settings set them; each overrides the project variable of the same key for that analysis. Read-only. Returns a JSON string array of { key, value, sourceType } entries, or [] when none are set; secret values (e.g. passwords) read as "***". Use wopee_fetch_analysis_suites to discover suite UUIDs.

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>"
    },
    "name": "wopee_fetch_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesWhich variable set to read. PROJECT reads the project-level variables (the connected project). ANALYSIS reads a specific analysis suite's variables and requires suiteUuid.
suiteUuidNoUUID of the analysis suite to read variables from. Required when level is ANALYSIS; ignored when level is PROJECT.

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 read. PROJECT reads the project-level variables (uses WOPEE_PROJECT_UUID from the environment). ANALYSIS reads a specific analysis suite's variables and requires suiteUuid."New value: +"Which variable set to read. PROJECT reads the project-level variables (the connected project). ANALYSIS reads a specific analysis suite's variables and requires suiteUuid."
  2. Changed1 schema field changedv1.32.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Addedv1.29.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds materially: the return shape ({ key, value, sourceType }), the empty-array case, secret masking as "***", and the precedence rule that analysis-level values override project variables of the same key. Those are behavioral facts no structured field carries.

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 core action and the read-only guarantee, then the return contract, then the sibling pointer. The level: ANALYSIS clause packs many ideas into one long sentence, which is dense but not wasteful; nearly every phrase carries information.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing the returned array, its fields, the empty case, and secret redaction. Combined with per-level behavior and the UUID discovery path, an agent has everything needed to call this correctly on the first attempt.

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 the baseline is 3, but the description goes beyond the enum labels by explaining what each level actually reads and how the analysis-level result relates to the project level via key-level override. That interpretation guidance is real added meaning, though suiteUuid's 'ignored when PROJECT' behavior is already in the schema.

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?

States a specific verb and resource ('Read the run-time variables (additionalVariables)') plus the scope ('at either level'), and distinguishes itself from the sibling mutator by declaring 'Read-only'. An agent can tell this is the variable-inspection tool without opening the schema.

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 branching guidance per level: PROJECT for project-level variables, ANALYSIS for a suite and 'requires suiteUuid'. It also routes the agent to wopee_fetch_analysis_suites to discover suite UUIDs. It doesn't explicitly exclude any case or name wopee_update_variables as the alternative for writing, so it falls just short of full when/when-not coverage.

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