Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

by ptamb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Shortcut Iterations

list_iterations

Retrieve all iterations (sprints) in your Shortcut workspace to monitor sprint progress and plan upcoming cycles.

Instructions

List iterations (sprints) in your Shortcut workspace.

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": "list_iterations"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states 'List iterations' without revealing return format, pagination, or the existence of a dry_run parameter. It does not disclose any behavioral traits beyond the basic action.

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 sentence with no fluff or redundant wording, making it highly concise. However, while it is well-structured, it is so brief that it omits critical information, which slightly detracts from its effectiveness.

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 list tool, the description is incomplete: it fails to mention the dry_run parameter and any behavioral aspects like result set or filtering. Given the lack of annotations and output schema, the description should provide more context but does not, leaving the agent uncertain about how the tool behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one property 'dry_run' with no description (0% schema description coverage), and the tool description does not mention or explain this parameter. Since the description does not compensate for the missing schema documentation, the parameter semantics are completely opaque.

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 'List' and the resource 'iterations (sprints)' within the 'Shortcut workspace', which specifically differentiates it from sibling tools like list_projects or list_members. It uses a specific verb+resource pattern that leaves no ambiguity about what the tool does.

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?

There is no guidance on when to use this tool versus alternatives such as get_iteration or get_iteration_stories. The description implies usage for listing all iterations, but it does not provide explicit context, exclusions, or mention of alternatives, leaving the agent to infer.

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