Skip to main content
Glama
Sign In
opencode-subagent-mcp

opencode-subagent-mcp

by sebstaq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Stop an opencode subagent

stop

Abort a running opencode subagent to get its partial output. Works even if the agent ID predates an MCP server restart.

Instructions

Abort a running opencode subagent. Returns what it produced so far. agent_ids from before a restart of the MCP server still work.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral burden and does add real value: it says the call returns partial output produced so far and that IDs survive an MCP server restart. It does not state whether the abort is irreversible, whether it errors on finished agents, or any permission requirements, leaving gaps for a mutation-style tool.

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?

Three short sentences, front-loaded with the action, then the return behavior, then the edge-case note. Nothing is padded; it is appropriately sized for a one-parameter tool.

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?

With no annotations and no output schema, the description covers the core action, the partial-result return, and the restart edge case. It still omits idempotency, failure modes when the agent is already stopped, and error semantics — meaningful gaps for a termination operation.

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 0% and agent_id is undocumented in the schema, but the description adds genuine meaning about it — that IDs minted before a server restart remain valid. That is one useful semantic detail, though it does not fully document format or validity expectations for the single parameter.

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 (abort) and resource (running opencode subagent), and clarifies it stops an in-flight subagent rather than waiting on or messaging one. It stops short of explicitly naming which sibling to use instead, so it is clear but not sibling-routing.

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 'running opencode subagent' implies the condition for use, but no alternative is named (e.g., when to use stop vs wait), and there is no guidance on what to do if the agent is not running or has already finished.

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

Deploy Server

Other Tools