Skip to main content
Glama

OpenCode status

opencode_status
Read-only

Reports whether the MCP bridge is configured and connected to an OpenCode v2 server, even when no configuration exists. Call it first to diagnose connection issues.

Instructions

Report whether this MCP bridge is configured and connected to an OpenCode v2 server. Works even when nothing is configured, so it is the first tool to call when something looks wrong.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

readOnlyHint=true already establishes this is a safe read. The description adds a genuinely non-obvious trait beyond the annotations: it succeeds even when no configuration exists, so the agent knows a failure here means something deeper is broken rather than a setup gap. It does not describe the shape of the reported status.

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, front-loaded with what it reports and followed by the operational cue. No filler, no restating the tool name, and every sentence adds information.

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 simple read-only health check, the definition covers purpose, safety, and invocation timing, and no output schema exists to lean on. The only real gap is that it never hints at what the status report contains (configured vs connected vs version/error detail), which would help an agent interpret the result.

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?

The tool takes zero parameters, so the schema carries no semantics to compensate for; baseline 4 applies. The description correctly implies it requires no input, which is consistent with the empty properties object.

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 verb and object: report whether the MCP bridge is configured and connected to an OpenCode v2 server. Among a sibling set of action tools (session_*, agent, model, etc.), this is unmistakably the diagnostic/status tool, so no schema inspection is needed to tell it apart.

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?

Gives explicit timing guidance: call it first when something looks wrong, and it works even with nothing configured. It does not name a specific alternative or state when-not to call it, but for a zero-parameter diagnostic the when-to-use guidance is clear and actionable.

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