Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

by ptamb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Iteration Stories

get_iteration_stories

Fetch all stories belonging to a given Shortcut iteration ID. Use to review iteration progress, plan work, and ensure nothing is missed.

Instructions

List all stories in a Shortcut iteration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "iteration_id": "<iteration_id>"
    },
    "name": "get_iteration_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
iteration_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior. It states the read operation but does not mention pagination, return format, or the effect of the dry_run parameter, which is especially relevant given the schema includes it.

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, front-loaded sentence with no filler; it communicates the core operation efficiently. However, it omits parameter and usage details, but those are separate concerns.

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 tool with no annotations, no output schema, and two parameters only one of which is obvious, the description is too sparse. It fails to explain dry_run behavior or the shape of the returned story list, leaving significant gaps for an agent.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate. It only loosely implies that iteration_id specifies the iteration, and provides no explanation for dry_run. This is insufficient for an agent to populate parameters correctly.

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 uses a specific verb ('List') and resource ('stories in a Shortcut iteration'), making the operation clear. It distinguishes from sibling tools like get_iteration (iteration details) and list_iterations (iteration list).

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?

No guidance is provided about when to use this tool instead of alternatives like search_stories or list_epic_stories. The context of needing all stories for a specific iteration is only implied by the name and description, not stated explicitly.

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