Skip to main content
Glama

create_task

Create a task. Link it to an epic with epicId (omit for a standalone task). status defaults to 'open'. Adding an open task to a finished epic ('acceptance'/'ready') sends it back to 'designed' — don't add follow-up work there; use a standalone task or a new epic instead. Never create tasks for deploying/rolling out or for an acceptance checklist. If the user is working inside a VSCode workspace and a <workspace>/.bilg/bilg.config.json exists, prefer that file's projectName over the API key's default project. If .bilg/bilg.config.json has a "surface" and the new item concerns only that part, set surfaces to it; omit surfaces on a task to inherit its epic's. Descriptions are summaries. If the task has a detailed spec, create a document and link it with documentId. Work only on items assigned to the user unless told otherwise; see list_tasks assignee='me'. When setting status to 'blocked', include a blockedReason. Don't invent priority — leave it unset if unknown.

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": {
      "title": "<title>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
typeNo
titleYes
epicIdNoLink to this epic
labelsNoFree-form tags, e.g. ['ui', 'auth']
statusNo
assigneeNo"me", a person's name, the email shown for members without a name, or id, or null. Defaults to unassigned (inherits from the epic owner).
priorityNo
surfacesNoSurface names or ids this task concerns. Replaces the full set; [] = inherit the epic's surfaces.
subNumberNoSub-number within the epic, e.g. '13.1'
documentIdNoLink a detail/spec document. Pass null to unlink.
descriptionNo
projectNameNo
blockedReasonNoWhy the task is blocked. Only used when status is 'blocked'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / surfaces
      Added value: +{
      +  "description": "Surface names or ids this task concerns. Replaces the full set; [] = inherit the epic's surfaces.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the status default, the side effect that adding an open task to an acceptance/ready epic resets it to 'designed', surface inheritance from the epic, the blockedReason requirement, and the instruction not to invent priority. It stops short of stating what is returned or any permission/ownership requirements beyond the assignment policy.

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?

Front-loaded with the core action, then layered with constraints; nearly every sentence contributes a non-obvious rule. It is long (roughly ten sentences) and a couple of items, such as the assignment policy, read as general workflow doctrine rather than call-specific guidance.

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?

For a 14-parameter mutation tool with no annotations and no output schema, the description covers the risky decision points (epic status side effects, surfaces inheritance, blocked reasons, spec-vs-summary). The remaining gaps are the return value and the meaning of size/type/labels, which are largely inferable from enums.

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 coverage is 50%, and the description compensates for the most ambiguous parameters: epicId omission semantics, status default and blocked coupling, surfaces inheritance/replacement, documentId as the place for detailed specs while description stays a summary, and priority restraint. It adds nothing for size, type, labels, or subNumber, leaving a portion of the schema gap unfilled.

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?

Opens with a specific verb+resource ("Create a task") and immediately clarifies the key structural relationship to a sibling resource: tasks link to an epic via `epicId` or stand alone. An agent can distinguish this from create_epic, create_document, or create_decision without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states when NOT to use it (never for deploy/rollout or acceptance checklists; don't add follow-up work to a finished epic — use a standalone task or new epic), and names a concrete alternative workflow ("see list_tasks assignee='me'"). It also gives a precedence rule for projectName when a workspace config file exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources