Skip to main content
Glama

processInstance_getVariables

Retrieve all variables for an active process instance, including each variable's name, type, and value, to inspect current execution state.

Instructions

Retrieve all variables for an active process instance. Returns each variable with its name, type, and value. Use to inspect current execution state.

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": {
      "id": "<id>"
    },
    "name": "processInstance_getVariables"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
deserializeValuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / properties / deserializeValues
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does say the tool returns name, type, and value for each variable and scopes results to 'active' instances, which is useful, but it does not say what happens for completed instances, whether values are truncated or serialized, or what permissions are needed.

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?

Three short sentences, front-loaded with the core action, with no repetition of the tool name. The return-value sentence and the usage sentence are both compact; the whole block is appropriately sized for a simple read tool.

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

Completeness3/5

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

For a two-parameter read with no output schema, the description covers purpose and the general return shape adequately. It falls short on the undocumented `deserializeValues` flag and on any behavior for non-active instances, which are real gaps given zero annotation and schema coverage.

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 description coverage is 0%, so the description must explain both parameters and does not. The `id` parameter is only obliquely implied by 'process instance', and the `deserializeValues` boolean — the one parameter whose meaning is genuinely non-obvious — is never mentioned at all.

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 and resource ('Retrieve all variables for an active process instance') and clarifies scope with 'all', which implicitly separates it from the singular processInstance_getVariable. It does not name that sibling outright, so differentiation requires a small inference.

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?

'Use to inspect current execution state' implies a context but gives no explicit when-not guidance and no named alternative (e.g., the single-variable sibling). An agent must infer the choice from the word 'all'.

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