Skip to main content
Glama

escalate

Raise blockers, ambiguity, resource, conflict, assistance, or emergency issues when blocked or unclear; route to the correct owner, and pause blocking tasks until resolved.

Instructions

Raise an escalation when you are blocked or something is unclear. kind: blocker, ambiguity, resource, conflict, assistance or emergency; with: orchestrator, management, team, agent or path_owner (target: the agent or path). blocking: true blocks your task: end your turn with a one-line summary and you will be resumed with the resolution. emergency: money, credentials, scope or human_action.

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": {
      "execution_id": "<execution_id>",
      "agent_token": "<agent_token>",
      "kind": "<kind>",
      "with": "<with>",
      "summary": "<summary>"
    },
    "name": "escalate"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
withYes
targetNo
optionsNo
summaryYes
blockingNoDefault false.
questionNo
emergencyNo
agent_tokenYesThe agent token join_execution returned (once).
diagnosticsNo
execution_idYesThe heads-down run (exe-…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, it discloses the non-obvious control-flow contract: blocking=true halts the task, requires ending the turn with a one-line summary, and the agent is resumed with the resolution. It also adds the emergency channel's meaning. This is exactly the kind of behaviour an agent cannot infer from the schema.

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?

Front-loads the purpose and then packs enumerations tersely; no filler sentences. The semicolon-and-colon shorthand ('kind: …; with: …') is dense but still parseable, and the blocking behaviour is given its own clause rather than being buried.

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 an 11-parameter mutation tool with a nested diagnostics object and no output schema, the description covers the critical blocking lifecycle but says nothing about what diagnostics should contain, when to supply options/question, or what an escalation returns. Adequate for basic invocation, incomplete for confident full use.

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 only 27%, so the description must compensate. It does explain kind's six values, with's five values, target ('the agent or path'), blocking's effect, and emergency's four values, but leaves options, summary, question, diagnostics and the token/execution id params to the schema. Roughly half the parameters get no added meaning.

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 ('Raise an escalation') plus the triggering condition ('when you are blocked or something is unclear'). An agent can identify the function immediately, though it never explicitly distinguishes it from neighbours like post_update or chat_completion, which could also be used to surface a problem.

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 clear when-to-use context: blocked or unclear situations, with enumerated kinds and recipients that map the situation to the right escalation channel. It stops short of stating when NOT to escalate or naming an alternative tool for non-escalation communication.

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