@createworker/mcp

Official

by CreateWorkerAI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

List workers

workers_list

List AI workers in your organization. Retrieve worker IDs to create tasks for them.

Instructions

List the org's AI workers. Use a worker's id to create tasks for it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workers_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided. The description only says 'list' without disclosing that it is a read-only, safe operation, or explaining pagination behavior via cursor and limit.

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?

Two efficient sentences front-loading purpose and use case. No wasted words, but could be slightly expanded to include parameter hints without losing conciseness.

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

Completeness2/5

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

Despite simplicity, the description omits return format, pagination details, and filtering options. With no output schema, the agent lacks necessary context for correct invocation.

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

Parameters1/5

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

Schema has 3 parameters with 0% description coverage. The description does not explain the meaning or usage of limit, cursor, or status, leaving the agent without guidance on how to filter or paginate.

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 explicitly states the tool lists AI workers and explains its purpose (getting IDs for task creation). It clearly distinguishes from siblings like worker_get and tasks_list.

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 implies when to use (to get worker IDs for task creation) but does not explicitly mention when not to use or provide alternatives like worker_get for a single worker.

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