Skip to main content
Glama
Sign In

Laraue Boards

by com.laraue
OverviewDiscussionsAdmin

list_epics

Lists epics - of one space, or of every space the caller can read - up to 50 per page, ordered by space key - check hasNextPage for more. Each epic has its id (what list_issues' epicId filter accepts), name, spaceKey, isDefault (the space's backlog epic) and status, derived from its issues: New (no issues, or all of them in a Created status), Done (all of them Completed) or Active (anything else).

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page number - pass the previous result's page + 1 for the next page. Omit for the first page.
countNoMax epics per page, 1-50. Omit for the default of 50.
spaceKeyNoOnly epics of this space, e.g. 'BRD', from list_spaces. Omit to list epics of every space.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

No annotations, so the description carries full burden and delivers: ordering by space key, 50-per-page cap, hasNextPage pagination signal, and the status derivation rules (New/Done/Active). This is exactly the behavioral context an agent needs.

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?

Single dense sentence that front-loads scope and pagination, then enumerates returned fields. Information-dense but slightly packed; not wasteful.

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?

With no output schema and no annotations, the description fully compensates by describing return fields (id, name, spaceKey, isDefault) and derived status values. An agent has everything needed to call and interpret results.

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?

Schema coverage is 100% and already documents page, count, and spaceKey thoroughly. The description reinforces the 50 cap and links the returned id to list_issues' epicId, adding marginal semantic value over the schema.

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?

States a specific verb (lists) and resource (epics) plus scope (one space or all readable spaces). Clearly distinguishes it from list_issues by explaining the epicId link.

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?

Explains pagination behavior ('check hasNextPage for more') and cross-references list_issues' epicId filter, giving clear context. Does not explicitly state when to prefer list_issues over this tool, so not a full 5.

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

All Laraue Boards toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources