Skip to main content
Glama

Background job status

opencode_job

Track tasks started with background=true. Returns only the final summary once the job is done — intermediate tool calls and thinking never leave OpenCode.

Instructions

Track tasks started with background=true. Returns only the final summary once the job is done — intermediate tool calls and thinking never leave OpenCode.

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": "opencode_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIDNoRequired for status and cancel
limitNo
actionNoDefault: status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

B3.2/5.0
Behavior3/5

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

With only readOnlyHint=false supplied, the description adds meaningful behavior: results are only the final summary and intermediate tool calls/thinking are withheld. That is useful context an agent cannot get from annotations. But it never discloses that cancel is a state-changing, likely irreversible action, nor anything about polling cadence, timeouts, or what a not-yet-done response looks like.

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 tight sentences, front-loaded with the precondition and followed by the return-value guarantee. No redundant restatement of the name or title and nothing padding the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 must carry the full burden for a three-action tool with a mutation path. It covers only the status/tracking case and is silent on list, on cancel semantics, and on the limit parameter, leaving an agent without enough to invoke non-status actions correctly.

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

Parameters2/5

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

Schema coverage is 67% and the description adds zero parameter guidance. jobID and action have schema descriptions, but limit (1-100) is undocumented in both places, and the description never explains that jobID is mandatory for status/cancel or how action defaults interact with listing.

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?

"Track tasks started with background=true" states a specific verb and resource and ties it to the background flag, giving an agent a clear handle on when this applies versus foreground task tools. It falls short of full clarity because the tool actually supports status, list, and cancel, and the description only describes tracking/status.

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?

The phrase "started with background=true" implies the precondition for using this tool, which is real guidance. However, there is no explicit when-not guidance, no mention of the list or cancel actions, and no alternative named (e.g., opencode_task or opencode_session_interrupt).

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