Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

Official
by useshortcut
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Iterations: Get Upcoming

iterations-get-upcoming
Read-onlyIdempotent

Retrieve upcoming iterations for your team to plan and track ongoing work. Filter by team ID to target specific projects.

Instructions

Get upcoming iterations for current user's teams.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "iterations-get-upcoming"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdNoTeam ID to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • changedInput schema / properties / teamId / description
      Previous value: -"The ID of a team to filter iterations by"New value: +"Team ID to filter by"
  2. Addedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe read operation. The description adds the behavioral context 'for current user's teams', but does not disclose additional traits such as result ordering, pagination, or what constitutes 'upcoming' (e.g., future start date, non-started).

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?

A single sentence with no filler words. All content is essential and front-loaded.

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?

For a simple read-only list tool with one optional parameter, the description provides the core functionality. However, it lacks any mention of return format (e.g., list of iteration objects) or any constraints (e.g., only returns non-completed iterations). Given the presence of sibling tools with similar functions, more context would help.

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 for the single parameter 'teamId' with 'Team ID to filter by'. The description adds no further meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'get', the resource 'upcoming iterations', and the scope 'for current user's teams'. It distinguishes from sibling tools like 'iterations-get-active' which retrieves active iterations, and 'iterations-search' which requires parameters.

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 alternative iteration retrieval tools such as 'iterations-get-active', 'iterations-get-by-id', or 'iterations-search'. The agent must infer from the name alone.

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

Deploy Server

Other Tools