Skip to main content
Glama

respond_to_job

Answer a paused browser job's prompt with CAPTCHA solutions or human decisions to resume it. Use it when a job waits for input before continuing.

Instructions

Answer an input_required prompt (CAPTCHA solution, human decision point). Flips the job back to running.

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": {
      "job_id": "<job_id>",
      "response": "<response>"
    },
    "name": "respond_to_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
responseYesYour answer to the agent's question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key side effect: the job flips back to running. It says nothing about permissions, what happens on an invalid or late response, or whether the answer is validated, which leaves meaningful behavioral gaps for a mutation tool.

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 compact sentences, no filler, with the trigger condition front-loaded and the resulting state change stated second. Nothing is redundant or buried.

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 two-parameter, no-output-schema tool this covers purpose, trigger, and post-call state. The main omission is how an agent learns a job is awaiting input in the first place, which would round out the picture.

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 coverage is 50%: 'response' is documented in the schema while 'job_id' is not. The description compensates somewhat by characterizing the response content (CAPTCHA answer, human decision), but adds no format, length, or matching guidance beyond that.

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 object ('Answer an input_required prompt') and gives concrete examples of what that means (CAPTCHA solution, human decision point). It is clearly distinct from siblings like run_task or get_job, though it never names them explicitly.

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?

Usage is implied by the precondition 'input_required prompt', which tells the agent the job must be in an awaiting-input state. However, it does not say how to detect that state (e.g., via get_job) or what to do if the job is not awaiting input, and no alternatives are named.

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