Skip to main content
Glama

job_update_context

Update the job context by merging new data. Existing keys are preserved unless explicitly overwritten. Use this to record progress, update assignment statuses, or store intermediate results.

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": {
      "updates": "<updates>"
    },
    "name": "job_update_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoOmit it: the run's own job is used.
updatesYesKey-value pairs to merge into job context
trace_idNoOnly for a session working an agent task DialogBrain handed to it: that task's Trace ID, which names the run's job and thread. Omit it inside an agent's own run.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / trace_id
      Added value: +{
      +  "description": "Only for a session working an agent task DialogBrain handed to it: that task's Trace ID, which names the run's job and thread. Omit it inside an agent's own run.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare it is a non-read, non-destructive, non-open-world mutation. The description adds the meaningful behavioral fact that updates merge rather than replace and that existing keys survive unless explicitly overwritten — exactly the risk an agent needs to know before calling. There is a mild tension with idempotentHint=false (a key-preserving merge looks idempotent), but it is not a clear contradiction since the server may apply other effects; return behavior is still undescribed.

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 action and the merge constraint before the use cases. No filler. A slightly tighter form would fold the use-case sentence into one clause.

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 mutation with no output schema, an agent needs to know the merge vs. replace behavior and the intended use cases — both are present, and the four parameters including the nested updates object are fully documented in the schema. Only the response shape and failure behavior are unaddressed.

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 100%, so job_id, trace_id, in_workspace, and the updates object are already documented in detail. The description adds no parameter-level meaning beyond referencing 'new data' generically. Baseline 3 is appropriate when the schema carries the load.

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 ('Update the job context') and immediately qualifies it with merge semantics, which distinguishes it from job_read_context. It is clear what the tool does, though it never explicitly contrasts itself with the read counterpart.

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 concrete triggers: recording progress, updating assignment statuses, storing intermediate results. That is a solid when-to-use signal. There is no explicit when-not-to-use or named alternative, so it stops short of the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.