Skip to main content
Glama
Sign In
shortcut-mcp

shortcut-mcp

by idyll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create-epic

Create a new epic in Shortcut by providing a name, description, and optional milestone ID.

Instructions

Create a new epic in Shortcut

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": {
      "name": "<name>",
      "description": "<description>"
    },
    "name": "create-epic"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesEpic name
descriptionYesEpic description
milestone_idNoOptional milestone ID to associate with the epic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

C2.7/5.0
Behavior1/5

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

No annotations are present, and the description fails to disclose behavioral traits such as idempotency, side effects, authentication requirements, rate limits, or what happens upon creation. The bare statement 'Create a new epic' is insufficient.

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 very short and front-loaded, with no wasted words. While it could benefit from slight expansion, it is not overly verbose.

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?

Despite 100% schema coverage, the description lacks critical context: no output format, no success/failure hints, no mention of required permissions, and no explanation of the milestone_id parameter's significance. The tool has 3 parameters and no output schema, so more detail is needed.

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%, so baseline is 3. The description does not add any meaning beyond the schema's parameter descriptions; it repeats no new information.

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 it creates a new epic in Shortcut, specifying the resource and action. It is distinct from siblings like create-objective or create-story, though it lacks additional context about what an epic is.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or exclusions.

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