Skip to main content
Glama
Sign In
zube-mcp

zube-mcp

by reenrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_epic_cards

Retrieve every card assigned to an epic. Provide the epic ID and adjust page/per_page parameters to control output.

Instructions

List all cards belonging to an epic.

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": {
      "epic_id": "<epic_id>"
    },
    "name": "list_epic_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
epic_idYes
per_pageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It claims 'all cards' but fails to disclose pagination (page/per_page), whether archived cards are included, or that iteration is needed to fetch truly all cards. This is a significant gap for a list operation.

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 a single six-word sentence with no superfluous content, directly front-loading the core action and resource.

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

Completeness2/5

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

The description is too thin for a paginated list tool. It fails to clarify what 'belonging to an epic' means (direct cards vs all descendants), does not mention pagination defaults, and provides no context beyond the tool name. The output schema exists but does not compensate for missing usage context.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation of epic_id, page, or per_page. The phrase 'all cards' even contradicts the need for pagination, leaving parameter semantics entirely unspecified.

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 'List all cards belonging to an epic' uses a specific verb and resource, clearly distinguishing this tool from generic list_cards or list_project_cards by the epic scope.

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?

Implies usage when needing cards for a specific epic, but does not explicitly state alternatives or exclusions (e.g., use list_cards for all cards). No when-not-to-use guidance is provided.

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