Skip to main content
Glama

epic_update

Idempotent

Modify epic details in Saga MCP's project tracker by specifying only the fields to change, including status updates to manage workflow or soft-delete items.

Instructions

Update an epic. Pass only the fields you want to change. Set status to "cancelled" to soft-delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEpic ID
nameNo
descriptionNo
statusNo
priorityNo
sort_orderNo
tagsNo

Implementation Reference

  • The handler function that executes the logic for updating an epic.
    function handleEpicUpdate(args: Record<string, unknown>) {
      const db = getDb();
      const id = args.id as number;
    
      const oldRow = db.prepare('SELECT * FROM epics WHERE id = ?').get(id) as Record<string, unknown> | undefined;
      if (!oldRow) throw new Error(`Epic ${id} not found`);
    
      const update = buildUpdate('epics', id, args, ['name', 'description', 'status', 'priority', 'sort_order', 'tags']);
      if (!update) throw new Error('No fields to update');
    
      const newRow = db.prepare(update.sql).get(...update.params) as Record<string, unknown>;
      logEntityUpdate(db, 'epic', id, newRow.name as string, oldRow, newRow, ['name', 'status', 'priority']);
    
      return newRow;
    }
  • The MCP tool definition and input schema for the epic_update tool.
    {
      name: 'epic_update',
      description:
        'Update an epic. Pass only the fields you want to change. Set status to "cancelled" to soft-delete.',
      annotations: { title: 'Update Epic', readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'integer', description: 'Epic ID' },
          name: { type: 'string' },
          description: { type: 'string' },
          status: { type: 'string', enum: ['planned', 'in_progress', 'completed', 'cancelled'] },
          priority: { type: 'string', enum: ['low', 'medium', 'high', 'critical'] },
          sort_order: { type: 'integer' },
          tags: { type: 'array', items: { type: 'string' } },
        },
        required: ['id'],
      },
    },
  • Registration of the epic_update tool handler within the exported handlers object.
    export const handlers: Record<string, ToolHandler> = {
      epic_create: handleEpicCreate,
      epic_list: handleEpicList,
      epic_update: handleEpicUpdate,
    };
Behavior4/5

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

The description adds valuable behavioral context beyond the annotations: it explains the partial update behavior ('Pass only the fields you want to change') and reveals that setting status to 'cancelled' performs a soft-delete operation. While annotations already indicate this is a non-destructive, idempotent mutation, the description provides specific implementation details about update semantics and soft-delete functionality.

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 extremely concise with just two sentences that both add value. The first sentence establishes the core functionality, and the second provides important behavioral context about partial updates and soft-delete. Every word serves a purpose with zero waste.

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 mutation tool with 7 parameters, low schema coverage (14%), and no output schema, the description is somewhat incomplete. While it provides good behavioral context about partial updates and soft-delete, it doesn't address important aspects like error conditions, what happens with invalid parameters, or the format of the response. The annotations help but don't fully compensate.

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?

With only 14% schema description coverage (only the 'id' parameter has a description), the description doesn't provide meaningful semantic information about most parameters. It mentions the 'status' field's special 'cancelled' value but doesn't explain other parameters like 'priority', 'sort_order', or 'tags'. The description doesn't adequately compensate for the low 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 ('Update an epic') and the resource ('epic'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'task_update' or 'project_update' beyond the epic focus.

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 provides some usage guidance ('Pass only the fields you want to change') and mentions a specific use case for the status field ('Set status to "cancelled" to soft-delete'). However, it doesn't explicitly state when to use this tool versus alternatives like 'epic_create' or how it differs from other update tools in the system.

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