Skip to main content
Glama

job_read_context

Read the current job context. Returns the full state of your active job including assignments, escalations, and any data you previously stored.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_read_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoOmit it: the run's own job is used.
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

C2.8/5.0
Behavior1/5

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

The description frames this as a pure observation ("Read the current job context. Returns the full state..."), but the annotations declare readOnlyHint=false and idempotentHint=false, so the tool may actually mutate or store state and repeat calls are not guaranteed equivalent. The description discloses none of that, so an agent would treat it as a side-effect-free read when the structured metadata says otherwise.

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?

Two sentences with the resource front-loaded and the return contents spelled out immediately; no filler. It is short enough to scan in one pass, though it spends its budget on return contents while omitting call conditions.

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?

Without an output schema, the description usefully says what the state contains, and all three parameters are self-documenting. It remains incomplete for a tool whose annotations mark it non-read-only and non-idempotent, because no side effects or repeat-call behavior are described.

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 all three optional parameters, including the subtle in_workspace note ("Nothing is stored; other sessions are not affected"), are already documented in the schema. The description adds no parameter meaning beyond that, which matches the baseline 3 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?

The description gives a specific verb-plus-resource ("Read the current job context") and then enumerates the payload it returns: assignments, escalations, and previously stored data. That distinguishes it adequately from job_update_context by name semantics, though it never explicitly contrasts the two.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance appears. The agent must infer that this is a state-orientation call to make before acting on a job, and nothing steers it toward job_update_context versus this reader or explains prerequisites.

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.