Skip to main content
Glama
Sign In
contextium-mcp-server

contextium-mcp-server

Official
by contextium-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

break_down_task

Analyzes a broad task and automatically generates 3-6 actionable subtasks to make it manageable. Uses context from task title and workflow.

Instructions

Use AI to break a broad task into 3-6 concrete, actionable subtasks. Claude analyses the task title and workflow context, then creates the subtasks automatically. Use when a task is too broad to complete in one step.

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>",
      "workflowId": "<workflowId>"
    },
    "name": "break_down_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesID of the parent task to break down.
workflowIdYesWorkflow ID that owns the task.
workspaceIdNoWorkspace ID. Defaults to your configured workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided. Description says it 'creates subtasks automatically' but does not disclose if existing subtasks are replaced, idempotency, permissions, or side effects. Key behavioral details missing.

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?

Two sentences, front-loaded, no fluff. Efficient and clear.

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

Completeness3/5

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

Covers purpose and usage, but lacks description of return value/output (no output schema) and error conditions. Partial completeness.

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 100% with descriptions for each parameter. Description does not add meaning beyond schema; baseline 3 is appropriate.

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?

Clearly states it breaks a broad task into 3-6 concrete subtasks, distinguishing it from sibling tools like add_task or update_task.

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?

Provides clear when-to-use guidance ('Use when a task is too broad to complete in one step') but lacks explicit when-not-to-use or alternatives.

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