Skip to main content
Glama

epic_create

Group related tasks into a feature or workstream by creating an epic within a project. Organizes project tracking by structuring work into manageable components.

Instructions

Create an epic within a project. Epics group related tasks into a feature or workstream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesParent project ID
nameYesEpic name
descriptionNoEpic description
statusNoplanned
priorityNomedium
tagsNo

Implementation Reference

  • The handler function that executes the logic to create an epic in the database.
    function handleEpicCreate(args: Record<string, unknown>) {
      const db = getDb();
      const projectId = args.project_id as number;
      const name = args.name as string;
      const description = (args.description as string) ?? null;
      const status = (args.status as string) ?? 'planned';
      const priority = (args.priority as string) ?? 'medium';
      const tags = JSON.stringify((args.tags as string[]) ?? []);
    
      const epic = db
        .prepare(
          'INSERT INTO epics (project_id, name, description, status, priority, tags) VALUES (?, ?, ?, ?, ?, ?) RETURNING *'
        )
        .get(projectId, name, description, status, priority, tags);
    
      const row = epic as Record<string, unknown>;
      logActivity(db, 'epic', row.id as number, 'created', null, null, null, `Epic '${name}' created in project ${projectId}`);
    
      return epic;
    }
  • The tool definition and input schema for epic_create.
    {
      name: 'epic_create',
      description: 'Create an epic within a project. Epics group related tasks into a feature or workstream.',
      annotations: { title: 'Create Epic', readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'integer', description: 'Parent project ID' },
          name: { type: 'string', description: 'Epic name' },
          description: { type: 'string', description: 'Epic description' },
          status: {
            type: 'string',
            enum: ['planned', 'in_progress', 'completed', 'cancelled'],
            default: 'planned',
          },
          priority: {
            type: 'string',
            enum: ['low', 'medium', 'high', 'critical'],
            default: 'medium',
          },
          tags: { type: 'array', items: { type: 'string' } },
        },
        required: ['project_id', 'name'],
      },
    },
  • Registration of the handleEpicCreate function to the epic_create tool key.
    epic_create: handleEpicCreate,
Behavior3/5

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

Annotations cover key traits (readOnlyHint=false, destructiveHint=false, etc.), so the description doesn't need to repeat those. It adds context about epics grouping tasks, which helps understand the tool's purpose, but doesn't disclose additional behavioral aspects like error conditions, permissions needed, or what happens on success.

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 two concise sentences that efficiently convey the tool's purpose and the concept of epics. It's front-loaded with the main action and avoids unnecessary details, though it could be slightly more structured (e.g., separating purpose from context).

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?

For a creation tool with no output schema and moderate complexity (6 parameters, 2 required), the description is minimal. It covers the basic purpose but lacks details on usage context, parameter guidance, or expected outcomes. Annotations help, but the description alone is insufficient for full understanding.

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 50%, with parameters like 'project_id' and 'name' well-described but others like 'tags' lacking. The description doesn't add any parameter-specific information beyond what's in the schema, so it doesn't compensate for the coverage gap. Baseline 3 is appropriate given partial schema coverage.

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 ('Create an epic') and resource ('within a project'), and explains what epics are ('group related tasks into a feature or workstream'). However, it doesn't explicitly differentiate from sibling tools like 'epic_update' or 'project_create' beyond the verb 'Create'.

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 like 'epic_update' or 'project_create', nor does it mention prerequisites (e.g., needing an existing project). It only states what the tool does, not when it's appropriate.

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/spranab/saga-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server