Skip to main content
Glama
Sign In
sandraschi

opencode-cli-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

opencode_mcpb_install

OPENCODE_MCPB_INSTALL - Install an MCPB bundle into opencode config.

Instructions

OPENCODE_MCPB_INSTALL - Install an MCPB bundle into opencode config.

Unpacks the .mcpb (or reads an unpacked directory), extracts the manifest, and merges the server definition into the opencode config file's mcp section.

Return Format

{"success": bool, "server_name": str, "config_path": str, "entry": {...}}

Examples

opencode_mcpb_install(source="./dist/arxiv-mcp-v1.0.0.mcpb") opencode_mcpb_install(source="./dist/arxiv-mcp-v1.0.0.mcpb", name_override="arxiv") opencode_mcpb_install(source="./mcpb/", dry_run=True)

Input Schema

NameRequiredDescriptionDefault
sourceYesPath to an .mcpb file or an unpacked MCPB directory.
dry_runNoShow what would be written without modifying the config.
name_overrideNoOverride the server name in opencode config. Default: from manifest.

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.11
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
+  "data": {
+    "type": "object"
+  },
+  "message": {
+    "type": "string"
+  },
+  "success": {
+    "type": "boolean"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "success",
+  "message",
+  "data"
+]
  2. First observedv0.2.3

TDQS

A4.1/5.0
Behavior4/5

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

With only `readOnlyHint: false` in annotations, the description carries most of the behavioral burden and does well: it explains that the tool unpacks/reads a bundle, extracts a manifest, and merges a server definition into the config file. It does not explicitly describe overwrite/conflict behavior for existing server entries, but the mutation and `dry_run` semantics are sufficiently clear.

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 description is front-loaded with purpose and workflow, then provides return format and examples. It is generally well-structured and efficient, though the return format section is partly redundant because an output schema exists.

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?

Given the tool has an output schema, full parameter description coverage, and a clear mutation annotation, the description is nearly complete. It explains the mutation workflow and return shape; the main remaining gap is not explaining how existing server name conflicts are handled.

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%, and the schema already documents `source`, `dry_run`, and `name_override` meaningfully. The description's examples demonstrate usage scenarios but do not add significant parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 and resource: installing an MCPB bundle into opencode config. It also explains the core workflow—unpacking the bundle or reading a directory, extracting the manifest, and merging the server definition into the config's `mcp` section—so an agent can understand exactly what the tool does.

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 clearly establishes the context: use this when installing an MCPB bundle or unpacked MCPB directory into opencode config. The examples reinforce usage, but there are no explicit exclusions or alternative tools for other installation paths.

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

Deploy Server

Other Tools