Skip to main content
Glama

list_epics

List epics of a project, in order. Each epic shows its progress (idea/designed/[acceptance]/ready/deployed — acceptance only if the project enables it, see the Stages: line), plan horizon (later/next/now/done), and whether it's currently being worked on. If the user is working inside a VSCode workspace and /.bilg/bilg.config.json has a "surface", pass it as surface unless the user asks for the whole project. If the user is working inside a VSCode workspace and a <workspace>/.bilg/bilg.config.json exists, prefer that file's projectName over the API key's default project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_epics"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoLabel (comma-separated for several): only items carrying one of them.
surfaceNoSurface name or id (comma-separated for several); "all" = the whole project. Shows items on that surface plus project-wide items. Defaults to the connection's surface, if any.
projectNameNoDefaults to the API key's default project

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / label
      Added value: +{
      +  "description": "Label (comma-separated for several): only items carrying one of them.",
      +  "type": "string"
      +}
    • addedInput schema / properties / surface
      Added value: +{
      +  "description": "Surface name or id (comma-separated for several); \"all\" = the whole project. Shows items on that surface plus project-wide items. Defaults to the connection's surface, if any.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return content and ordering, and clarifies the conditional acceptance stage via the `Stages:` line, which is real added context. It never states that this is a read-only operation, says nothing about result limits or pagination, and does not say what an empty or invalid project yields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and return-shape sentence is front-loaded and earns its place. The two trailing conditionals are near-duplicates in structure ("If the user is working inside a VSCode workspace and ..." repeated twice) and could be merged into one tighter sentence; the parenthetical about the `Stages:` line is also opaque without seeing the output.

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

Completeness4/5

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

With no output schema and no annotations, the definition must describe the result itself, and it does: per-epic progress, horizon, and active-work status. What remains unaddressed is volume/ordering guarantees and permission or failure behavior, but for a zero-required-parameter list tool the coverage is solid.

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 coverage is 100%, so baseline is 3. The description goes beyond the schema by giving a resolution rule for `surface` (workspace config value unless the user asks for the whole project) and for `projectName` (prefer the workspace config file over the API key default), which the schema only hints at. It adds nothing about `label`, but that parameter is already well documented in the schema.

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?

States a specific verb and resource ("List epics of a project, in order") and then enumerates what each returned epic contains (progress stage, plan horizon, active-work flag), which lets an agent predict the response shape. It is clearly distinguishable from the get_epic sibling, but the differentiation is only implicit — no sibling is named.

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 conditional VSCode-workspace guidance tells the agent when to pass `surface` and which `projectName` to prefer, which is genuine usage context. However, there is no guidance on when to choose list_epics over list_tasks, search_documents, or get_epic, and no statement of when not to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources