opencode-workbench

Workbench server info

describe_workbench

Read-onlyIdempotent

Describe this MCP server from its bundled profile without contacting any target or making a network call: repository URL, the default component set, components grouped by tier (required/core/optional), and optional MCP add-ons. It takes no parameters, is always safe, and returns instantly. Use it first to resolve a component id for install_component/remove_component/update_component or to see available add-ons; use inspect_target for a machine's live state.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`repo`	Yes	Web URL of the workbench repository.
`repoGit`	Yes	Git clone URL of the workbench repository.
`versions`	No	Summary of the bundled workbench.versions.json, when present.
`components`	Yes	Every component with id, tier and description.
`optionalMcp`	Yes	Optional MCP add-on ids available in the profile.
`packageRoot`	Yes	Filesystem path of the installed package.
`defaultComponents`	Yes	Component ids installed by default.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedOutput schema / properties / versions

Added value: +{
+  "additionalProperties": false,
+  "description": "Summary of the bundled workbench.versions.json, when present.",
+  "properties": {
+    "mcp": {
+      "description": "MCP servers recorded across every install class.",
+      "type": "number"
+    },
+    "opencode": {
+      "description": "OpenCode CLI version the profile records as current.",
+      "type": "string"
+    },
+    "repo": {
+      "description": "Version of this package.",
+      "type": "string"
+    },
+    "skills": {
+      "description": "Agent skills in the bundled profile.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "repo",
+    "mcp",
+    "skills"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes beyond the readOnlyHint/idempotentHint annotations by declaring no target contact, no network call, and instant return — operational facts the annotations do not carry. It stops short of describing the shape or size of the returned profile, which an agent deciding whether to dump it might want, so it is strong but not exhaustive.

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 is returned, then the routing guidance. Every clause carries information: profile contents, no-parameter behavior, safety, speed, and the sibling split against inspect_target.

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?

An output schema exists, so return-value explanation is not required — yet the description still names the key fields, which helps an agent decide when to call it. For a parameterless, side-effect-free, statically-backed tool, nothing needed for correct invocation is missing.

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?

Zero-parameter tool, so the baseline is 4; the description reinforces this with "It takes no parameters," removing any doubt. There is nothing further to clarify semantically.

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+resource ("describe this MCP server from its bundled profile") and enumerates exactly what is returned: repository URL, default component set, components by tier, and optional add-ons. It explicitly contrasts itself with inspect_target ("live state"), so an agent can separate the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it first to resolve a component id for install_component/remove_component/update_component or to see available add-ons" gives explicit when-to-use plus the sibling tools that depend on its output. "use inspect_target for a machine's live state" names the alternative and the condition that selects it.

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

All opencode-workbench tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.