Skip to main content
Glama

Coline

List cycles

list_cycles
Read-onlyIdempotent

Lists cycles the person can open: for them, their teams, projects and the whole workspace.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
cyclesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's added value is that results are filtered by access rights across person/team/project/workspace scopes, which matters for interpreting empty results, but it says nothing about pagination, ordering, or result size.

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?

A single front-loaded sentence with no filler; the verb and the access-scope qualifier arrive immediately. Brevity costs a little clarity since the scoping clause is compressed into a colon list.

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?

An output schema exists and annotations carry the safety profile, so return values and permissions need no prose. However, for a three-parameter tool with a partially documented schema, the description leaves the scopeId/scopeKind relationship and any result-set limits unaddressed.

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 33%: workspace is documented in the schema, while scopeId and scopeKind are not. The description partially compensates by enumerating the four access levels (them, their teams, projects, whole workspace), which maps onto the scopeKind enum values, but scopeId is never explained nor is the pairing requirement between scopeKind and scopeId.

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?

"Lists cycles the person can open" gives a specific verb plus resource and immediately bounds the result set, which separates it from mutation siblings like start_cycles. It falls short of a 5 because "cycles" is never defined and no sibling list_* tool is named for contrast.

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?

The visibility phrasing ("the person can open") implies this is the discovery call before acting on a cycle, but there is no explicit when-to-use, when-not-to-use, or named alternative. Guidance must be inferred from the stated scope rather than read directly.

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