Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

get-epic

Retrieve Shortcut epic details using its public ID to access project management information and track progress.

Instructions

Get a Shortcut epic by public ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
epicPublicIdYesThe public ID of the epic to get

Implementation Reference

  • The handler function that executes the 'get-epic' tool logic: fetches the epic using the Shortcut client, checks for existence, and formats the result using base utilities.
    async getEpic(epicPublicId: number) {
    	const epic = await this.client.getEpic(epicPublicId);
    
    	if (!epic) throw new Error(`Failed to retrieve Shortcut epic with public ID: ${epicPublicId}`);
    
    	return this.toResult(
    		`Epic: ${epicPublicId}`,
    		await this.entityWithRelatedEntities(epic, "epic"),
    	);
    }
  • Registers the 'get-epic' MCP tool with the server, including name, description, input schema, and thin wrapper handler delegating to getEpic method.
    server.tool(
    	"get-epic",
    	"Get a Shortcut epic by public ID",
    	{ epicPublicId: z.number().positive().describe("The public ID of the epic to get") },
    	async ({ epicPublicId }) => await tools.getEpic(epicPublicId),
    );
  • Zod schema for the input parameter 'epicPublicId' used in the tool registration.
    { epicPublicId: z.number().positive().describe("The public ID of the epic to get") },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits such as error handling (e.g., what happens if the ID is invalid), response format, rate limits, or authentication requirements. This leaves significant gaps for an agent to understand how to use it effectively.

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 ('Get a Shortcut epic by public ID') with zero wasted words. It's appropriately sized for a simple retrieval tool with one parameter.

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 low complexity (one parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose but lacks context on behavior, output, or integration with siblings. Without annotations or output schema, more detail on what the tool returns would be helpful for completeness.

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%, with the parameter 'epicPublicId' fully described in the schema. The description adds no additional meaning beyond what the schema provides (e.g., no context on ID format or sourcing). Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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 epic'), specifying it's by 'public ID'. It distinguishes from siblings like 'search-epics' by focusing on retrieval of a single epic rather than searching. However, it doesn't explicitly contrast with 'get-story' or other get-* tools beyond the resource type.

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 when you have a specific epic's public ID, as opposed to 'search-epics' for broader queries. However, it lacks explicit guidance on when to use this versus 'get-story' or other retrieval tools, and doesn't mention prerequisites like authentication or access rights.

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