Skip to main content
Glama
Sign In
@createworker/mcp

@createworker/mcp

Official
by CreateWorkerAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Archive worker

worker_delete

Archive a worker by its ID, marking it as inactive without permanent deletion.

Instructions

Archive (soft-delete) a worker.

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": {
      "workerId": "<workerId>"
    },
    "name": "worker_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
workerIdYesthe worker id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions 'soft-delete' which implies reversible action, but lacks details on consequences, permissions, or whether the action is idempotent. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but may sacrifice necessary detail. It is front-loaded and structured, but could benefit from more context.

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?

Given low complexity, the description is incomplete. It does not explain what 'archive' entails, return value, or side effects. No output schema, so more detail needed.

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%, so the schema documents the only parameter. The description does not add meaning beyond 'the worker id'. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it archives (soft-deletes) a worker. The verb is specific and the resource is clear. However, it does not explicitly differentiate from sibling tools like worker_delete (if exists) or worker_update, but the soft-delete nuance provides some distinction.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, when not to use, or context for soft-deletion versus hard deletion. The description is purely declarative.

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

Deploy Server

Other Tools