Skip to main content
Glama

job_escalate

Escalate the job to a human. Use when you cannot resolve an issue, someone is not responding, or a situation requires human judgment.

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": {
      "reason": "<reason>"
    },
    "name": "job_escalate"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoOmit it: the run's own job is used. Never pass a thread or message id here.
reasonYesWhy escalation is needed
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds trigger context but never says what escalation actually does: whether the run pauses or terminates, whether the agent should stop working afterward, or who is notified. For a terminal-looking workflow action, that outcome is the key missing behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, action first and conditions second, with no filler or repetition. Every clause carries information the agent can act on.

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?

The tool is simple, has one required parameter, full schema coverage, and no output schema, so most of the burden is already met. The remaining gap is behavioral: the description does not tell the agent what state the job enters after escalation or whether it should continue working, which is central to using an escalation tool correctly.

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%, and the schema itself carries strong per-parameter guidance (omit job_id, never pass a thread or message id, trace_id only for handed-off tasks). The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 states a specific verb and resource ('Escalate the job to a human'), so the operation is unambiguous. It does not differentiate itself from plausible siblings such as agent_handoff or agents_ask, leaving the agent to infer which escalation path applies.

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?

It gives three concrete trigger conditions: unresolvable issue, unresponsive party, and need for human judgment. It stops short of exclusions or naming an alternative tool, so the agent still has to decide between this and sibling handoff/ask tools on its own.

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.