Skip to main content
Glama
mryesiller

opencode-delegate-mcp

by mryesiller

List available provider/model ids

list_models
Read-onlyIdempotent

Retrieve provider/model ids for OpenCode delegation tasks. Filter by provider, substring, or limit to find the right model for cost-effective task distribution.

Instructions

List provider/model ids that OpenCode can use, in "provider/model" form (e.g. "minimax-coding-plan/MiniMax-M2.5-highspeed"). Optionally filter to a single provider. Use these ids for the model argument of delegate_task or as default_model in set_delegate_config.

Args:

  • provider (string): Optional provider id to filter by (e.g. "minimax-coding-plan", "openrouter").

  • contains (string): Optional case-insensitive substring filter.

  • limit (number): Max ids to return (default 200).

  • response_format ('markdown' | 'json'): Output format (default 'markdown').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax ids to return
containsNoCase-insensitive substring filter
providerNoFilter to a single provider id
response_formatNomarkdown
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by explaining return format and filtering behavior, without contradicting annotations.

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?

Concise and well-structured with an introductory sentence and bullet list for parameters. No redundant 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?

For a simple list tool with readOnly/idempotent hints and no output schema, the description covers all necessary aspects: purpose, parameters, output format, and usage context.

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?

Description adds examples and clarifies defaults for all 4 parameters. Schema has 75% coverage with descriptions; description compensates for the gap by adding examples and context, though defaults are already in schema.

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 states it lists available provider/model IDs, gives an example format, and explains their use with `delegate_task` or `set_delegate_config`, distinguishing it from sibling 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?

Description specifies when to use (to get model IDs for delegation) and mentions optional filtering. It lacks explicit when-not or alternatives, but 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