Skip to main content
Glama

Coline

Propose a cycle plan

propose_cycle_plan
Read-onlyIdempotent

Proposes what goes in a cycle: tasks due in it, open promises due in it, milestone tasks dated in it and what rolled over. The backlog lists the rest of the scope's open tasks by priority. Each person shows their tasks in the cycle and their free days in the window.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
cycleYes
peopleYes
backlogYes
proposedYes
promisedWithoutTaskYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description goes further by disclosing the composition of the proposal — due tasks, open promises, dated milestone tasks, rollovers, priority-ordered backlog, and per-person free days — which is the behavior an agent needs to interpret the result. It does not say whether the proposal is stored or requires an existing cycle, which is the main remaining gap.

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?

Three tight sentences, front-loaded with the core action and then the output composition. The middle sentence about the backlog is slightly orphaned since it describes output, not action, but no wording is wasted.

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?

With an output schema present, return values need not be explained, yet the description spends most of its length on exactly that while leaving prerequisites (does the cycle need to exist?) and parameter meaning unaddressed. It is adequate for a two-parameter read tool but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: workspace carries a slug hint, but cycleId has no description in either the schema or the description. The description never mentions either parameter, so it adds no meaning about how a cycle is identified or what happens with an invalid cycleId.

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 opens with a specific verb and resource: 'Proposes what goes in a cycle,' and then enumerates the constituents (due tasks, open promises, milestone tasks, rollovers, backlog, per-person availability). An agent can tell this computes a proposed plan rather than reading an existing one, though it never uses a term like 'plan' or 'draft' that maps directly to the tool name.

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?

There is no when-to-use guidance: nothing says to call this before set_cycle_tasks, how it differs from read_cycle, or whether the proposal is persisted. The closing sentence about backlog and per-person output implies a planning/review context but stops short of stating it.

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