Skip to main content
Glama

opencode bridge diagnostics

opencode_status
Read-onlyIdempotent

Checks the opencode setup without using quota, covering bridge and opencode versions, credentials, available models, and data location, to diagnose 'not found' errors and flag updates.

Instructions

Check the opencode setup. Spends no quota; run it first when a call says "not found". Its bridge version row says when a newer agent-intern release is out: if so, tell the user. Also checks opencode's version (1.x or 2.x), configured credentials ("none" is fine: the free models still answer), the model ids available, and where opencode keeps its data.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.30.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: zero quota cost, the fact that 'none' credentials still work with free models, and how to act on the 'bridge version' row when a newer release exists. It does not cover failure behavior or what the response looks like, so it is additive but not rich.

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?

The purpose and the no-quota cost are front-loaded, and each following clause carries distinct diagnostic content rather than filler. The middle sentence is densely packed with multiple ideas, which slightly hurts scannability but nothing is redundant.

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?

For a zero-parameter, read-only diagnostic with an output schema already describing the returned rows, the description supplies everything needed to call it at the right moment and to interpret the result. It even prescribes a follow-up action for the version-check outcome.

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 there is no parameter semantics to explain; this is the baseline case where the definition cannot lose points for parameter documentation.

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?

The opening sentence 'Check the opencode setup' gives a specific verb and resource, and the follow-up enumerates exactly what is inspected (bridge version, opencode version 1.x/2.x, credentials, available model ids, data location). It is clearly distinct from the ask/continue siblings, though it does not explicitly contrast itself with the other *_status diagnostics tools.

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?

It gives a concrete trigger condition — 'run it first when a call says "not found"' — plus the reassurance that it 'spends no quota', which removes the main reason an agent might hesitate to call a diagnostic. There is no explicit guidance on when not to use it, nor a named alternative.

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