Skip to main content
Glama

OpenCode Info

opencode-info
Read-only

Retrieve this server's configuration and OpenCode's current catalogs (models, agents, roots) without starting a session. Use it to check limits, defaults, and available resources.

Instructions

Discover this server's configuration and OpenCode's current catalogs without starting a session. section "server" (default) reports this server's version, mode, defaults and limits (maxOutputChars, maxBatchIds, output retention, request-id table size, …); "models" and "agents" list what OpenCode currently advertises for a given cwd; "roots" lists this server's allowed working-directory roots. "models"/"agents"/"roots" are paginated (offset/limit) and return a snapshot-id to keep reading the same consistent snapshot; pagination arguments are invalid for "server". Read-only; the "server" section never starts OpenCode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoOnly for models/agents: which OpenCode directory instance to query (same resolver as opencode's cwd). Omit to use the server default cwd.
limitNoOnly for models/agents/roots: how many items to return in this page (1-100, default 50).
offsetNoOnly for models/agents/roots: item offset to resume a paginated read from (default 0).
sectionNoWhat to look up (default "server"): "server" for this server's version/mode/defaults/limits, "models"/"agents" for what OpenCode currently advertises, "roots" for the allowed working-directory roots. Pagination arguments (offset/limit/snapshot-id) are invalid for "server".
providerNoOnly for models: restrict the list to one provider id.
snapshot-idNoOnly for models/agents/roots, required once offset > 0: the id from a prior page of the same read, so pagination stays consistent with one snapshot instead of a live-changing catalog.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
costNo
diffNo
hintNo
kindYes
turnNo
agentNo
errorNo
modelNo
rootsNo
totalNo
actionNo
agentsNo
finishNo
modelsNo
offsetNo
outputNo
reasonNo
serverNo
statusYes
tokensNo
turnIdNo
cleanupNo
contentYes
hasMoreNo
partialNo
requestNo
resultsNo
sectionNo
waitForNo
readyIdsNo
sessionsNo
threadIdNo
warningsNo
directoryNo
elapsedMsNo
sessionIdNo
toolCallsNo
truncatedNo
nextOffsetNo
observedAtNo
pendingIdsNo
snapshotIdNo
availabilityNo
filesChangedNo
resendSafetyNo
responseLoopNo
upstreamReadNo
omittedFieldsNo
toolCallCountNo
upstreamRetryNo
executionStateNo
opencodeVersionNo
pendingApprovalsNo
structuredOutputNo
filesChangedCountNo
abortedRunningTurnNo
pendingApprovalCountNo
structuredOutputErrorNo
structuredOutputStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare read-only and open-world behavior, and the description adds meaningful context beyond them: the server section never starts OpenCode, paginated sections use a snapshot-id for consistency, and pagination arguments are invalid for the server section. These details help an agent invoke the tool safely and correctly.

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?

The description is front-loaded with the tool's purpose and then efficiently details sections, pagination, and read-only behavior. Despite covering multiple modes, it is dense without being bloated, and every clause adds useful 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?

With an output schema present and annotations covering safety, the description supplies the remaining behavioral context an agent needs: section semantics, pagination behavior, and the no-session guarantee. Nothing critical for correct invocation is missing.

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 documents all six parameters in detail. The description reinforces cross-parameter rules such as pagination validity and snapshot-id usage, but it largely repeats or summarizes what the schema already provides.

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 opens with a specific verb and resource: discovering this server's configuration and OpenCode's current catalogs. It also distinguishes the tool from siblings by explicitly noting it works without starting a session, which separates it from opencode or session-oriented 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 clear use conditions for each section and clarifies that 'server' reports local configuration while models/agents/roots query OpenCode catalogs. It does not explicitly name sibling alternatives or state when not to use this tool, but the operational context is clear.

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