Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

iterations-get-upcoming

Retrieve upcoming Shortcut iterations for your team to plan project timelines and track sprint schedules.

Instructions

Get the upcoming 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

  • Implements the core logic for retrieving upcoming Shortcut iterations, either for a specific team or all teams the current user belongs to, using the ShortcutClientWrapper. Handles errors, formats results, and includes related entities.
    async getUpcomingIterations(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.getUpcomingIteration([teamId]);
    		const iterations = result.get(teamId);
    		if (!iterations?.length)
    			return this.toResult(`Result: No upcoming iterations found for team.`);
    		if (iterations.length === 1)
    			return this.toResult(
    				"The next upcoming iteration for the team is:",
    				await this.entityWithRelatedEntities(iterations[0], "iteration"),
    			);
    		return this.toResult(
    			"The next upcoming 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.getUpcomingIteration(teamIds);
    	const allUpcomingIterations = [...resultsByTeam.values()].flat();
    
    	if (!allUpcomingIterations.length)
    		return this.toResult("Result: No upcoming iterations found for any of your teams.");
    	return this.toResult(
    		"The upcoming iterations for all your teams are:",
    		await this.entitiesWithRelatedEntities(allUpcomingIterations, "iterations"),
    	);
    }
  • Registers the 'iterations-get-upcoming' tool on the MCP server with input schema validation using Zod and links to the handler method.
    server.addToolWithReadAccess(
    	"iterations-get-upcoming",
    	"Get the upcoming 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.getUpcomingIterations(teamId),
    );
  • Zod schema for input parameters: optional teamId string.
    	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 ('Get') but doesn't disclose behavioral traits like whether it's read-only, pagination behavior, rate limits, authentication requirements, or what happens if no team memberships exist. The description is minimal and lacks essential operational context.

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 wasted words. It's front-loaded with the core purpose and includes necessary scope information. Every element earns its place without redundancy or unnecessary elaboration.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'upcoming' means temporally, how iterations are determined, what data is returned, or error conditions. For a tool with no structured behavioral hints, more contextual information is needed for effective agent use.

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 fully documents the optional 'teamId' parameter. The description adds no additional parameter semantics beyond implying team-based filtering through 'based on their team memberships', which aligns with but doesn't expand upon the schema. Baseline 3 is appropriate when schema coverage is complete.

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 ('upcoming Shortcut iterations') with scope ('for the current user based on their team memberships'). It distinguishes from siblings like 'iterations-get-active' by specifying 'upcoming' rather than 'active', but doesn't explicitly contrast with other iteration tools like 'iterations-search'.

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 context ('for the current user based on their team memberships') but doesn't explicitly state when to use this tool versus alternatives like 'iterations-search' or 'iterations-get-active'. It mentions team-based filtering but doesn't provide clear exclusion criteria or comparison with sibling tools.

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/useshortcut/mcp-server-shortcut'

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