Skip to main content
Glama
mryesiller

opencode-delegate-mcp

by mryesiller

Update the delegate configuration

set_delegate_config
Idempotent

Change active delegation settings at runtime to dynamically switch cheap model or provider without reinstalling. Only passed fields update; returns updated config.

Instructions

Change the active delegation settings at runtime — this is how you dynamically switch the cheap model or provider without reinstalling. Only the fields you pass are updated. Returns the updated config.

Args (all optional):

  • default_model (string): provider/model used when a call omits one, e.g. "openrouter/minimax/minimax-m2.5".

  • default_agent (string): default OpenCode agent.

  • default_variant (string): default reasoning-effort variant.

  • auto_approve (boolean): auto-approve tool permissions for delegations.

  • timeout_ms (number): per-delegation timeout in milliseconds.

  • default_directory (string): default working directory.

  • opencode_bin (string): path/name of the opencode binary.

  • profiles (object): map of name -> { model?, agent?, variant?, autoApprove? }. Profiles are MERGED, not replaced — existing ones are kept unless you name them. To ADD or UPDATE a profile, give it a value; to REMOVE one, set its value to null: { "profiles": { "tests": null } }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profilesNoNamed presets to merge in; set a name's value to null to remove that profile
timeout_msNo
auto_approveNo
opencode_binNo
default_agentNo
default_modelNoprovider/model default
default_variantNo
default_directoryNo
Behavior5/5

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

Annotations indicate mutable, idempotent, non-destructive. The description adds critical detail: runtime dynamic switching, partial updates, profile merging (not replacement), and null-based removal. This enriches the annotation signals without contradiction.

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 well-structured: purpose first, then partial update note, then parameter list. Every sentence adds value without redundancy. It is sufficiently detailed yet concise.

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?

Despite 8 optional parameters and nested objects, the description covers all fields and behavior (merge/remove). It states the return value ('Returns the updated config'), fulfilling completeness for a configuration update tool without output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low (25%), but the description compensates by explaining all 8 parameters, including the complex profiles object (merge vs remove behavior). It adds clear examples (e.g., 'openrouter/minimax/minimax-m2.5') and specific usage notes.

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 clearly identifies the tool's function: 'Change the active delegation settings at runtime' with a specific verb ('change') and resource ('delegate configuration'). It distinguishes itself from sibling tools (e.g., get_delegate_config, delegate_task) by focusing on updating configuration.

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 provides operational guidance: 'Only the fields you pass are updated' and explains profile merging and removal behavior. However, it does not explicitly contrast with siblings like get_delegate_config for reading or delegate_task for delegation, though the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mryesiller/opencode-delegate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server