@createworker/mcp

Official

Overview Schema Source Related Servers Discussions Admin

Create worker

worker_create

Create a worker by providing a name and role key, such as OPERATIONS_ASSISTANT, to assign predefined autonomy and capabilities.

Instructions

Create a worker. roleKey is a CreateWorker role (e.g. OPERATIONS_ASSISTANT, CUSTOMER_SUPPORT_AGENT, RESEARCH_ANALYST). Autonomy defaults per role.

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": {
      "name": "<name>",
      "roleKey": "<roleKey>"
    },
    "name": "worker_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	display name
`roleKey`	Yes	role key, e.g. OPERATIONS_ASSISTANT

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided. The description discloses that autonomy defaults per role, which is behavioral context. However, it does not mention idempotency, destructive operations, or side effects. The description carries the burden but only partially.

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 verb and object, no wasted words. Efficient and clear.

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 no output schema and no annotations, the description covers the essential functionality and parameter semantics. However, it lacks information about return values or required permissions, which would improve completeness.

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?

Schema covers 100% of parameters with basic descriptions. The description adds value by providing concrete examples for roleKey and explaining that autonomy defaults per role, going beyond the schema's generic description.

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 creates a worker, specifies the roleKey parameter with examples (OPERATIONS_ASSISTANT, CUSTOMER_SUPPORT_AGENT, RESEARCH_ANALYST), and mentions autonomy defaults per role. It is distinct from sibling tools like worker_delete or worker_update.

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

Usage Guidelines3/5

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

The description implies usage for creating workers but does not explicitly state when to use this tool versus alternatives, such as when to use worker_update for modifications. No exclusions or prerequisites are mentioned.

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