Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

get-iteration

Retrieve a specific iteration from Shortcut project management using its public ID to access detailed sprint information and progress data.

Instructions

Get a Shortcut iteration by public ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iterationPublicIdYesThe public ID of the iteration to get

Implementation Reference

  • Handler function that retrieves the iteration by public ID from the Shortcut client, handles errors, and formats the result using inherited methods from BaseTools.
    async getIteration(iterationPublicId: number) {
    	const iteration = await this.client.getIteration(iterationPublicId);
    
    	if (!iteration)
    		throw new Error(
    			`Failed to retrieve Shortcut iteration with public ID: ${iterationPublicId}.`,
    		);
    
    	return this.toResult(
    		`Iteration: ${iterationPublicId}`,
    		await this.entityWithRelatedEntities(iteration, "iteration"),
    	);
    }
  • Registration of the 'get-iteration' MCP tool, defining the name, description, input schema (iterationPublicId), and linking to the handler method.
    server.tool(
    	"get-iteration",
    	"Get a Shortcut iteration by public ID",
    	{
    		iterationPublicId: z.number().positive().describe("The public ID of the iteration to get"),
    	},
    	async ({ iterationPublicId }) => await tools.getIteration(iterationPublicId),
    );
  • Input schema for the 'get-iteration' tool using Zod validation for iterationPublicId.
    {
    	iterationPublicId: z.number().positive().describe("The public ID of the iteration to get"),
    },
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. It states the tool retrieves an iteration but doesn't describe what happens if the ID is invalid (e.g., error behavior), whether it's a read-only operation (implied by 'Get' but not explicit), or any rate limits or authentication requirements. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operational behavior.

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 that front-loads the core purpose without unnecessary words. Every element ('Get', 'Shortcut iteration', 'by public ID') earns its place by directly informing the tool's function. There is zero waste or redundancy.

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 the tool's simplicity (one required parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic 'what' but lacks context on error handling, return format, or integration with sibling tools. Without annotations or output schema, the agent must rely on the description and schema alone, which is sufficient for basic use but incomplete for robust operation.

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 schema description coverage is 100%, with the single parameter 'iterationPublicId' fully documented in the schema as 'The public ID of the iteration to get'. The description adds no additional semantic context beyond what the schema provides (e.g., format examples, ID sourcing, or uniqueness constraints). Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 ('a Shortcut iteration by public ID'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'get-active-iterations' or 'get-iteration-stories' by specifying retrieval of a single iteration via its public ID. However, it doesn't explicitly contrast with 'search-iterations' or explain why one would use this exact lookup versus a search approach.

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 alternatives. It doesn't mention prerequisites (e.g., needing a valid public ID), contrast with sibling tools like 'search-iterations' for broader queries, or indicate scenarios where this direct lookup is preferred over other retrieval methods. The agent must infer usage from the name and schema alone.

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