Kopern

kopern_run_team

Execute a multi-agent team on a prompt. Returns each agent's output and the final combined result using your API keys.

Instructions

Execute a multi-agent team on a prompt. Returns each agent's output and the final combined result. Uses YOUR API keys.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>",
      "prompt": "<prompt>"
    },
    "name": "kopern_run_team"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	The task/prompt to send to the team
`team_id`	Yes	The team ID or name

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.5Apr 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and openWorldHint=true. The description adds 'Uses YOUR API keys', which is a useful behavioral caveat (cost/security). However, it does not disclose other potential side effects or execution semantics beyond returning outputs, so it provides only partial transparency.

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 concise sentences, front-loaded with the primary action and outcome. No redundant wording or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description correctly explains return values. It mentions API key usage. However, it omits prerequisites (e.g., team must be created first), error conditions, and any potential side effects, leaving gaps for a multi-agent execution tool.

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 coverage is 100% with both parameters described ('prompt' and 'team_id'). The description does not add extra meaning beyond what the schema provides—it simply mentions a 'prompt' implicitly. Baseline 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 clearly states the verb 'Execute' and the resource 'multi-agent team on a prompt'. It also specifies the output: each agent's output and final combined result. This distinguishes it from siblings like kopern_run_pipeline and kopern_run_autoresearch.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives such as kopern_run_pipeline or kopern_create_team. It lacks any when-to-use or when-not-to-use context, prerequisites like 'team must exist', or exclusions.

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