Skip to main content
Glama

create_epic

Create an epic. progressStatus defaults to 'idea'; planStatus defaults to 'later'. deployed/done are not allowed on create — 'deployed' is not available to agents; the human sets it in the web UI. 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. If .bilg/bilg.config.json has a "surface" and the new item concerns only that part, set surfaces to it. Create the epic before starting non-trivial work. Put the summary here; put detail in a document and link it with documentId.

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": {
      "title": "<title>"
    },
    "name": "create_epic"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNo"me", a person's name, the email shown for members without a name, or id, or null. Defaults to unassigned (falls back to the project owner in solo projects).
titleYes
activeNo
labelsNoFree-form tags, e.g. ['ui', 'auth']. Replaces the full set.
surfacesNoSurface names or ids this epic touches. Replaces the full set; [] = project-wide.
documentIdNoLink a detail/spec document. Pass null to unlink.
planStatusNo
descriptionNoMarkdown description
projectNameNo
progressStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / labels
      Added value: +{
      +  "description": "Free-form tags, e.g. ['ui', 'auth']. Replaces the full set.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / surfaces
      Added value: +{
      +  "description": "Surface names or ids this epic touches. Replaces the full set; [] = project-wide.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: it declares defaults for progressStatus/planStatus and explicitly states 'deployed'/'done' are not allowed on create and that 'deployed' is not available to agents at all. It omits error behavior, uniqueness constraints on title, and what is returned, so not a 5.

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?

Dense but nearly every sentence carries actionable information, and the core verb/resource leads. A few clauses (workspace config, surfaces) are packed mid-paragraph, slightly hurting scannability, but there is minimal filler.

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?

For a 10-parameter mutation tool with no annotations and no output schema, the description covers the highest-risk semantics: enum defaults and the forbidden statuses. It does not address owner resolution or active/labels behavior, leaving partial gaps against 50% schema coverage.

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 50%, and the description compensates by explaining defaults for progressStatus and planStatus, the intended use of documentId for detail, and how projectName/surfaces should be derived from workspace config. It leaves owner, active, and labels semantics entirely to 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?

Opens with a specific verb+resource: 'Create an epic.' It adds scope guidance ('Put the summary here; put detail in a document and link it with documentId') that sharpens the resource. It doesn't explicitly distinguish create_epic from sibling create_task, so it stops short of a 5.

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?

Gives concrete when-to-use guidance ('Create the epic before starting non-trivial work') plus environment-specific routing for projectName and surfaces via .bilg/bilg.config.json. It never states when NOT to use it or how it differs from create_task, so no explicit alternatives.

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