Skip to main content
Glama

Coline

Start cycles

start_cycles

Starts cycles for a person (the caller), a team, a project or the whole workspace (admins): a length of one to six weeks, a start day, whether the next one is made automatically and whether unfinished tasks roll over.

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

Input Schema

NameRequiredDescriptionDefault
scopeIdNoThe team or project. Not needed for a person (yourself) or the workspace.
autoNextNo
rollOverNo
startDayNo0 is Sunday, 1 Monday.
scopeKindYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
lengthWeeksNo

Output Schema

NameRequiredDescriptionDefault
cycleYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=false. The description adds useful behavioral context beyond that: workspace scope requires admin rights, person scope defaults to the caller, autoNext controls automatic creation of the next cycle, and rollOver controls whether unfinished tasks carry over. It does not cover edge cases like existing cycles or error conditions.

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?

The description is a single front-loaded sentence with a compact list of configurable aspects and no wasted words. It could be slightly more readable if split into two sentences, but every clause carries information.

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?

Given a mutation tool with seven parameters, existing annotations, and an output schema, the description is largely complete: it covers scope targets, key behavioral flags, and the length constraint. It stops short of explaining side effects (task generation) or what happens when a cycle already exists, which would be helpful for a non-idempotent create operation.

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?

With 43% schema description coverage, the description compensates meaningfully by explaining autoNext ('whether the next one is made automatically') and rollOver ('whether unfinished tasks roll over'), and by restating the length constraint (one to six weeks). It also maps the scope options, though it leaves scopeKind enum details and some schema-documented fields to the schema.

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?

The description states a specific verb and resource ('Starts cycles') and immediately scopes it to person, team, project, or workspace, including the admin constraint. This clearly distinguishes it from a read-only sibling like list_cycles without needing to name alternatives.

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 verb and scope options, and the parenthetical '(admins)' gives a permission boundary. However, there is no explicit when-to-use versus alternatives, no exclusions (e.g., when not to start a cycle), and no mention of the sibling listing tool.

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