Skip to main content
Glama

Typebar (formerly SuperDocs)

continue_chat

Used with chat_async when a large edit paused to ask whether to keep going. Poll get_job until status=awaiting_approval AND metadata.awaiting_kind='continue_prompt'; then POST here with continue=true to resume (the AI picks up where it left off with a fresh time/step budget) or continue=false to stop (everything applied so far is kept). The job then resumes/finishes and reaches status=completed. This is NOT the change- approval endpoint (that is approve_change) — it can only act on a continue-prompt pause.

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": {
      "session_id": "<session_id>",
      "job_id": "<job_id>",
      "continue": "<continue>"
    },
    "name": "continue_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob ID awaiting a continue decision.
continueYesTrue to resume with a fresh budget; false to stop here (work so far is kept).
session_idYes
wait_for_resultNoDefault true: the call returns only after the resumed turn has settled (its changes applied and saved, a new pause, or a failure) and reports that outcome in job_status, applied and job. false returns at once (applied=false); then wait with get_job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that continue=true grants a fresh time/step budget, that continue=false keeps everything applied so far, and that the job then reaches status=completed. It omits auth requirements and idempotency of a repeated call, keeping it short of a 5.

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?

Front-loaded with the trigger condition, then the action, then the exclusion. Four dense sentences with no filler; the parenthetical clarifications all add information rather than restating.

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?

No output schema exists, and the description compensates by naming the resulting job states (awaiting_approval, completed, applied, job_status). The end-to-end flow — poll, decide, resume, settle — is complete enough to call correctly; only the shape of the returned job object is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and the description adds real meaning beyond it — the 'fresh time/step budget' semantics of continue=true and the 'work so far is kept' guarantee of continue=false. The wait_for_result tradeoff (block until settled vs applied=false then poll) is documented in the schema rather than the description, which is acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action (resume a paused large edit) tied to a specific resource (a job awaiting a continue prompt), and explicitly names the sibling it is not (approve_change). An agent can distinguish it from approve_change and get_job without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition — poll get_job until status=awaiting_approval AND metadata.awaiting_kind='continue_prompt' — and an explicit exclusion: it is NOT the change-approval endpoint. Both the when and the when-not are stated, plus the branch condition for true vs false.

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.