Skip to main content
Glama

Coline

Add tasks to a cycle

set_cycle_tasks

Puts tasks in a cycle or takes them out. A task is in at most one cycle per scope, so adding moves it from another cycle of the same scope.

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": {
      "workspace": "<workspace>",
      "cycleId": "<cycleId>",
      "taskIds": "<taskIds>"
    },
    "name": "set_cycle_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoadd
cycleIdYes
taskIdsYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
changedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses a genuinely non-obvious side effect: a task belongs to at most one cycle per scope, so an 'add' silently removes it from another cycle. That is exactly the kind of mutation risk an agent needs. It does not address permissions, partial-failure behavior for large batches, or why idempotentHint is false.

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 tight sentences with zero filler. The capability is stated first and the consequential side effect follows immediately, so the most important information is front-loaded.

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 mutation tool, the critical behavioral fact (cross-cycle relocation) is disclosed, and an output schema plus annotations carry the return shape and safety profile. Remaining gaps are minor: no mention of scope semantics for the workspace parameter or how a large taskIds batch is handled.

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 only 25%, but the description partly compensates by explaining the add/remove semantics that the action enum encodes. cycleId and taskIds remain meaningful only through their names, and constraints such as the 500-task limit and per-item length bounds are left entirely to the schema.

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?

States specific verbs and resource: 'Puts tasks in a cycle or takes them out', covering both the add and remove modes exposed by the action parameter. It does not name any sibling (e.g. add_tasks_to_project or propose_cycle_plan) to differentiate itself, so it is clear but not sibling-aware.

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?

Usage is implied by the semantics of moving tasks between cycles of the same scope, giving an agent a reasonable mental model of when this applies. There is no explicit when-to-use/when-not guidance and no named alternative for the adjacent cases (adding tasks to a project, reading a cycle).

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