Skip to main content
Glama
Sign In
Taskmaster

Taskmaster

by eyaltoledano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

scope_down_task

Simplify complex tasks efficiently with AI by adjusting their scope. Input task IDs, define strength levels, and apply custom prompts for precise task management in AI-driven development workflows.

Instructions

Decrease the complexity of one or more tasks using AI

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": {
      "id": "<id>",
      "projectRoot": "<projectRoot>"
    },
    "name": "scope_down_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoPath to the tasks file (default: tasks/tasks.json)
idYesComma-separated list of task IDs to scope down (e.g., "1,3,5")
projectRootYesThe directory of the project. Must be an absolute path.
promptNoCustom prompt for specific scoping adjustments
researchNoWhether to use research capabilities for scoping
strengthNoStrength level: light, regular, or heavy (default: regular)
tagNoTag context to operate on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'using AI' which hints at automation, but doesn't explain what 'decrease complexity' means operationally, whether changes are reversible, what permissions are needed, or how the tool interacts with the task system. Significant behavioral aspects remain undocumented.

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?

The description is a single, efficient sentence that communicates the core purpose without unnecessary elaboration. It's appropriately sized and front-loaded with the essential information.

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?

For a tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'decrease complexity' means in practice, what the expected outcome looks like, or how this tool differs from related task modification tools. The agent would need to guess about the tool's behavior and results.

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 description coverage is 100%, so parameters are well-documented in the schema itself. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 clearly states the action ('decrease complexity') and resource ('one or more tasks'), with the method ('using AI') providing additional context. However, it doesn't differentiate from sibling tools like 'scope_up_task' (which presumably increases complexity) or 'analyze_project_complexity' (which analyzes rather than modifies).

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 explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention sibling tools like 'scope_up_task' for increasing complexity or 'add_subtask' for breaking down tasks differently. Usage context is implied but not specified.

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

Related Tools