entherium_create_task

Status: GA Access: token required API contract: 0.3.0 · capability 2026-09-03.1 View as Markdown Open in Claude Open in ChatGPT

Create a TASK for a team member. assignee is a person’s NAME — it is resolved to that user; an unknown or ambiguous name is REJECTED (never silently unassigned). spec_ref TARGETS the task at a platform feature by its SPEC id (“SPEC-NNN”) so the work stays tied to the right feature context — pass it whenever the task is about a known spec; an unknown spec id is REJECTED. Needs the manage_task capability. Returns {“accepted”: true, “task_id”: } — KEEP the task_id to update / close / retarget / annotate it later; {“accepted”: false, “error”: …} otherwise.

Access: writes — the client asks you for confirmation before every call

Available at: /mcp/

Hints declared to MCP clients (ToolAnnotations)

Hint	Value
`readOnlyHint`	false
`destructiveHint`	false
`idempotentHint`	false
`openWorldHint`	false
`anthropic/requiresUserInteraction`	true

Parameters

Name	Type	Required	Description
`title`	`string`	yes	Task title
`description`	`string \| null`	no	What has to be done and why
`assignee`	`string \| null`	no	Team member’s display name; unknown or ambiguous names are rejected
`spec_ref`	`string \| null`	no	Feature id of the form SPEC-NNN the task targets; unknown ids are rejected

Example call

Send inside an initialized MCP session (see Connecting). Every parameter is shown with a typed placeholder; drop the optional ones you do not need — but for defect/task tools the QA fields are what keeps a report out of quarantine.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "entherium_create_task",
    "arguments": {
      "title": "<title>",
      "description": "<description>",
      "assignee": "<assignee>",
      "spec_ref": "<spec_ref>"
    }
  }
}

Returns

Field	Type	Description
`accepted`	`boolean` (optional)	True iff the write was applied / the report was taken in
`error`	`string` (optional)	Why it was not accepted (truthful, never a silent drop)
`task_id`	`integer` (optional)	Id of the created task (create_task only)

If it fails

Symptom	Cause	Action
`401`	Token missing/expired	Tokens are issued by the platform owner via `POST /api/v1/auth/agent-token` (superuser-only) — ask for a re-issue. ⚠️ A new token replaces your grant set
`403` / capability error	Your token lacks the capability or the contract grant	Check `my_capabilities` first; ask the owner for the grant