Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

get-active-iterations

Retrieve active Shortcut iterations for the current user's teams to track ongoing project cycles and sprints.

Instructions

Get the active Shortcut iterations for the current user based on their team memberships

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe ID of a team to filter iterations by

Implementation Reference

  • The main handler function that executes the tool logic: retrieves active Shortcut iterations for the current user's teams or a specific team using the ShortcutClientWrapper.
    async getActiveIterations(teamId?: string) {
    	if (teamId) {
    		const team = await this.client.getTeam(teamId);
    		if (!team) throw new Error(`No team found matching id: "${teamId}"`);
    
    		const result = await this.client.getActiveIteration([teamId]);
    		const iterations = result.get(teamId);
    		if (!iterations?.length) return this.toResult(`Result: No active iterations found for team.`);
    		if (iterations.length === 1)
    			return this.toResult(
    				"The active iteration for the team is:",
    				await this.entityWithRelatedEntities(iterations[0], "iteration"),
    			);
    		return this.toResult(
    			"The active iterations for the team are:",
    			await this.entitiesWithRelatedEntities(iterations, "iterations"),
    		);
    	}
    
    	const currentUser = await this.client.getCurrentUser();
    	if (!currentUser) throw new Error("Failed to retrieve current user.");
    
    	const teams = await this.client.getTeams();
    	const teamIds = teams
    		.filter((team) => team.member_ids.includes(currentUser.id))
    		.map((team) => team.id);
    
    	if (!teamIds.length) throw new Error("Current user does not belong to any teams.");
    
    	const resultsByTeam = await this.client.getActiveIteration(teamIds);
    
    	const allActiveIterations = [...resultsByTeam.values()].flat();
    
    	if (!allActiveIterations.length)
    		return this.toResult("Result: No active iterations found for any of your teams.");
    	return this.toResult(
    		`You have ${allActiveIterations.length} active iterations for your teams:`,
    		await this.entitiesWithRelatedEntities(allActiveIterations, "iterations"),
    	);
    }
  • Registration of the 'get-active-iterations' MCP tool using server.tool(), which includes the schema and references the handler method.
    server.tool(
    	"get-active-iterations",
    	"Get the active Shortcut iterations for the current user based on their team memberships",
    	{
    		teamId: z.string().optional().describe("The ID of a team to filter iterations by"),
    	},
    	async ({ teamId }) => await tools.getActiveIterations(teamId),
    );
  • Input schema for the tool: optional teamId string to filter iterations by team.
    {
    	teamId: z.string().optional().describe("The ID of a team to filter iterations by"),
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the tool retrieves data based on team memberships, but doesn't disclose behavioral traits like whether it requires authentication, returns paginated results, includes rate limits, or what 'active' means (e.g., time-based criteria). This is a significant gap for a tool with potential complexity.

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 with zero waste. It front-loads the core purpose and includes key constraints (current user, team memberships), making it easy to parse quickly.

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?

Given no annotations and no output schema, the description is minimally adequate but lacks details on return values, error handling, or behavioral nuances. It covers the basic purpose but doesn't fully compensate for missing structured data, leaving gaps for an AI agent to infer usage.

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 100%, so the schema already documents the optional 'teamId' parameter. The description adds context that iterations are filtered by the user's team memberships, implying 'teamId' further narrows this, but doesn't provide additional syntax or format details beyond what the schema offers.

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 ('active Shortcut iterations'), specifying they are for the current user based on team memberships. It distinguishes from siblings like 'get-iteration' (singular) and 'get-upcoming-iterations' (future-focused), but doesn't explicitly contrast with 'search-iterations' (which might allow broader filtering).

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 description implies usage when needing active iterations for the current user's teams, but doesn't explicitly state when to use this vs. alternatives like 'search-iterations' or 'get-upcoming-iterations'. No exclusions or prerequisites are mentioned, leaving some ambiguity about optimal tool 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/ampcome-mcps/shortcut-mcp'

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