Skip to main content
Glama
tacticlaunch

Linear

by tacticlaunch
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

linear_getCycleStats

Read-onlyIdempotent

Retrieve cycle statistics from Linear to analyze progress, scope, and team performance, enabling data-driven project decisions.

Instructions

Get statistics for a cycle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the cycle to inspect

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
numberNo
progressNo
issueCountNo
scopeHistoryNo
issueCountHistoryNo
completedIssueCountNo
completedScopeHistoryNo
completedIssueCountHistoryNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.4.2
    • changedOutput schema / properties / progress / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
  2. Changed1 schema field changedv1.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "completedIssueCount": {
+      "type": "number"
+    },
+    "completedIssueCountHistory": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "completedScopeHistory": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "issueCount": {
+      "type": "number"
+    },
+    "issueCountHistory": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "number": {
+      "type": "number"
+    },
+    "progress": {
+      "type": "number"
+    },
+    "scopeHistory": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. Addedv1.1.2

TDQS

C2.9/5.0
Behavior2/5

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

The description adds no behavioral information beyond what annotations already provide. Annotations indicate the tool is read-only and idempotent, but the description does not add context about what statistics are included or any constraints. It is not contradictory, but it does not enrich behavioral understanding.

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 concise sentence with no wasted words. However, it is so brief that it sacrifices useful context, so it does not earn a top score but is still appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one parameter and an output schema, the description is minimal. However, given the large number of cycle-related sibling tools, the lack of context on what distinguishes this from related tools makes it incomplete for correct selection.

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 coverage is 100%, and the description adds no additional information about the 'id' parameter. Since the schema fully documents the parameter, the description does not need to repeat it, but it also does not add any clarification about expected format or usage.

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 clearly states the tool retrieves statistics for a cycle, using a specific verb and resource. However, it does not differentiate from sibling tools like linear_getCycleById or linear_getActiveCycle, which also relate to cycles, so it falls short of a 5.

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?

No guidance is provided on when to use this tool versus alternatives. With many cycle-related siblings such as getCycleById, getActiveCycle, and getCycleIssues, an agent could easily be confused. The description offers no context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tacticlaunch/mcp-linear'

If you have feedback or need assistance with the MCP directory API, please join our Discord server