Skip to main content
Glama

linear_getActiveCycle

Retrieve the currently active work cycle for a Linear team to track ongoing project timelines and sprints.

Instructions

Get the currently active cycle for a team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdYesID of the team to get the active cycle for

Implementation Reference

  • Handler function that implements the core logic for the linear_getActiveCycle tool: validates input using type guard, calls LinearService.getActiveCycle(teamId), handles errors.
    export function handleGetActiveCycle(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isGetActiveCycleArgs(args)) {
            throw new Error('Invalid arguments for getActiveCycle');
          }
    
          return await linearService.getActiveCycle(args.teamId);
        } catch (error) {
          logError('Error getting active cycle', error);
          throw error;
        }
      };
    }
  • MCPToolDefinition for linear_getActiveCycle, specifying input_schema (requires teamId) and detailed output_schema for cycle object.
    export const getActiveCycleToolDefinition: MCPToolDefinition = {
      name: 'linear_getActiveCycle',
      description: 'Get the currently active cycle for a team',
      input_schema: {
        type: 'object',
        properties: {
          teamId: {
            type: 'string',
            description: 'ID of the team to get the active cycle for',
          },
        },
        required: ['teamId'],
      },
      output_schema: {
        type: 'object',
        properties: {
          id: { type: 'string' },
          number: { type: 'number' },
          name: { type: 'string' },
          description: { type: 'string' },
          startsAt: { type: 'string' },
          endsAt: { type: 'string' },
          team: {
            type: 'object',
            properties: {
              id: { type: 'string' },
              name: { type: 'string' },
              key: { type: 'string' },
            },
          },
          progress: { type: 'number' },
          issueCount: { type: 'number' },
          completedIssueCount: { type: 'number' },
        },
      },
    };
  • Registration of the linear_getActiveCycle handler within the registerToolHandlers function's returned object.
    linear_getCycles: handleGetCycles(linearService),
    linear_getActiveCycle: handleGetActiveCycle(linearService),
    linear_addIssueToCycle: handleAddIssueToCycle(linearService),
  • Type guard function isGetActiveCycleArgs used by the handler for input validation, ensuring teamId is a string.
    export function isGetActiveCycleArgs(args: unknown): args is {
      teamId: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'teamId' in args &&
        typeof (args as { teamId: string }).teamId === 'string'
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns error conditions, or details the output format. This is a significant gap for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action and target, making it highly concise and well-structured.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., cycle details, null if no active cycle) or behavioral aspects like error handling. For a tool with no structured support, more context is needed to be fully helpful.

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?

The input schema has 100% description coverage, with the 'teamId' parameter clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Get') and resource ('currently active cycle for a team'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'linear_getCycles' or 'linear_getTeams', which could provide similar or overlapping functionality, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'linear_getCycles' (which might list all cycles) or other team-related tools. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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