Skip to main content
Glama
spranab

Saga MCP

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

epic_list

Read-onlyIdempotent

List epics in a project, including task counts and completion stats, with filters for status, priority, or branch. Archived epics stay hidden unless explicitly included.

Instructions

List epics for a project with task counts and completion stats. Filter by status, priority or branch. Archived epics are hidden unless include_archived is set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchNoGit branch filter: "current" = active branch, "" = branch-agnostic only, omit = all.
statusNo
priorityNo
project_idYesProject ID
include_archivedNoInclude archived epics and their tasks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.10.0
    • changedInput schema / properties / branch / description
      Previous value: -"Filter by git branch. Pass \"current\" to auto-detect; pass empty string to list only branch-agnostic epics. Omit to list all."New value: +"Git branch filter: \"current\" = active branch, \"\" = branch-agnostic only, omit = all."
    • addedInput schema / properties / include_archived
      Added value: +{
+  "default": false,
+  "description": "Include archived epics and their tasks.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.5.5
    • addedInput schema / properties / branch
      Added value: +{
+  "description": "Filter by git branch. Pass \"current\" to auto-detect; pass empty string to list only branch-agnostic epics. Omit to list all.",
+  "type": "string"
+}
  3. First observedv1.5.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds behavioral context beyond the annotations by disclosing that archived epics are hidden by default unless include_archived is set, and that task counts and completion stats are included in the response.

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?

Two tight sentences: the first states the core action and return value, the second covers filtering and archived behavior. Every sentence earns its place with no filler or repetition of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool, the description covers the purpose, the key filters, the archived default, and the return's analytical value. No output schema exists, but the description sufficiently communicates what the agent will receive. There is no missing critical context needed to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 60%, with status and priority lacking descriptions. The description compensates by identifying these as filters and explaining the archived behavior. The branch parameter's nuanced values ('current', '', omit) are already documented in the schema, so the description need not repeat them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('List'), a clear resource ('epics for a project'), and the value-add ('task counts and completion stats'). This clearly distinguishes it from sibling tools like project_list, task_list, and the mutation-focused epic_create/epic_update/epic_archive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: listing epics with filtering by status, priority, or branch, and controlling archived visibility. It does not explicitly name alternatives or state when not to use it, but the resource and purpose are unambiguous enough for an agent to select it correctly.

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