Skip to main content
Glama
Sign In
@createworker/mcp

@createworker/mcp

Official
by CreateWorkerAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get task deliverables

task_deliverables

Retrieve the list of deliverables a task produced, showing the worker's output content.

Instructions

List the deliverables a task produced (the worker's output content).

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": {
      "taskId": "<taskId>"
    },
    "name": "task_deliverables"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesthe task id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses basic behavior (listing outputs), but lacks details like pagination, ordering, or handling of empty results.

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?

Single sentence, zero wasted words, front-loaded with action.

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?

Adequate for a simple list tool with one parameter and no output schema. Could mention ordering or behavior if no deliverables exist, but not essential.

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?

Only one parameter 'taskId' with description 'the task id'. Schema coverage is 100%, so description adds no extra meaning beyond the 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?

Description clearly states it lists deliverables produced by a task, using verb 'List' and specifying the resource 'deliverables' and context 'for a task'. It distinguishes from sibling 'deliverable_get' which likely gets a single deliverable.

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?

Description implies usage (when you need the output content of a task), but no explicit when-not or comparison to alternatives like 'deliverable_get'.

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