Skip to main content
Glama

Coline

Read a cycle

read_cycle
Read-onlyIdempotent

Reads a cycle: its window, progress, what was added after it started, the burn-up, each person's tasks in it and free days, and its review once written.

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": "read_cycle"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
cycleYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine value by disclosing the breadth of the returned payload, which signals that one call yields a lot and reduces the temptation to chain reads. It says nothing about permissions, workspace scoping, or cost, so it is additive but not rich.

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 the verb first and the payload list following; no filler or restatement of the title. The enumerated clauses are dense but each maps to a distinct piece of returned data. "Its review once written" is slightly elliptical but economically conveys conditional presence.

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, so the description need not explain return values, and annotations cover safety; for a simple two-parameter read the definition is close to sufficient. However, the missing cycleId sourcing guidance is a practical blocker for invocation. The description also assumes the reader knows what "free days" and "burn-up" mean in this product.

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 description pointing at workspaces.list, but cycleId is undocumented in both the schema and the description. The description says "a cycle" without explaining the ID's format or how to obtain it, so an agent has no route to a valid value. It does not compensate for the coverage gap.

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 names a specific verb and resource ("Reads a cycle") and then enumerates the payload: window, progress, post-start additions, burn-up, per-person tasks and free days, and the review. That is far more concrete than a tautology, and an agent can tell this is a read of a single cycle rather than a plan mutation like propose_cycle_plan. It stops short of explicitly contrasting itself with the write-side cycle siblings, which keeps it out of 5 territory.

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, no prerequisites, and no mention of alternatives such as propose_cycle_plan or set_cycle_tasks. The agent must infer from the name alone that this is the retrieval step before or after planning. Usage is only implied by the verb.

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