Skip to main content
Glama

task_setVariables

Add or update multiple typed variables on a user task so they remain available to the process after task completion.

Instructions

Add or update multiple variables on a user task. Variables set here are available in the process after task completion. Provide typed variable values.

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": "task_setVariables"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses that values propagate into the process on completion and that writes are upsert-style ("add or update"), but says nothing about overwrite-vs-merge conflict resolution, permission requirements, serialization of typed values, or failure behavior for invalid or completed tasks.

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 compact sentences, front-loaded with the operation and followed by the post-completion behavior. No filler, though the final sentence would earn its place only if the corresponding parameter were actually modeled.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the definition leaves critical gaps: the variable payload itself is not represented in the schema and the description does not compensate. An agent cannot confidently construct a valid call from this definition alone.

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 coverage is 0% and the schema exposes only a single undocumented "id" string, with additionalProperties left open. The description's instruction to "provide typed variable values" refers to input the schema never declares, so an agent gets no mapping between the described payload and any actual parameter.

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?

"Add or update multiple variables on a user task" gives a specific verb (add/update) and a specific resource and scope (user task variables), which separates it from processInstance_setVariables and task_getVariables. It stops short of explicitly naming those siblings.

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?

The note that variables become available in the process after task completion implies the task-scoped use case, but there is no explicit when-to-use versus processInstance_setVariables or task_getVariables, and no prerequisites (claim state, task existence) are stated.

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