opencode-mcp

opencode_events_poll

Read-onlyIdempotent

Poll OpenCode project or global events to monitor autonomous coding activity. Collect up to 1000 events within a set duration, reporting partial results on connection failures without stopping remote work.

Instructions

Poll project events from OpenCode, or explicitly select global scope. Collects up to maxEvents within the duration. Connection failures are reported with any partial events; stopping observation does not abort remote work.

Input Schema

TableJSON Schema

Name	Required	Description
`scope`	No	Event scope (default: project). Global events include all projects and cannot be combined with directory.
`directory`	No	Absolute path to the project directory. When provided, the request targets that project. If omitted, the OpenCode server uses its own working directory.
`maxEvents`	No	Maximum number of events to collect (default: 50, max: 1000)
`durationMs`	No	How long to collect events in milliseconds (default: 3000, max: 30000)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`text`	Yes
`isError`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Sep 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond annotations: connection failures return partial events, and stopping observation does not abort remote work. This helps an agent predict side effects and failure modes.

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 sentences with no filler. The core verb and resource are front-loaded, and the scope choice appears immediately. Every sentence contributes behavioral or usage information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose, scope variants, collection limits, failure behavior, and side-effect guarantees. With an output schema present and annotations covering safety, nothing essential is missing for an agent to invoke it correctly.

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 100%, so the schema already explains scope, directory, maxEvents, and durationMs. The description adds the relationship between maxEvents and duration, but this is marginal beyond the structured parameter descriptions.

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?

The description states a specific verb ('Poll'), a resource ('project events'), and an explicit scope option ('global scope'). It clearly distinguishes project-wide behavior from global behavior, so an agent understands exactly what the tool operates on.

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?

The description makes the primary usage clear: poll project events, or explicitly select global scope. It does not name alternative sibling tools, but no sibling directly competes with event polling, and the scope selection is stated upfront.

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

Deploy Server