Skip to main content
Glama
Sign In
HacknPlan MCP Server

HacknPlan MCP Server

by Lint111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_backlog

Retrieve work items with no board or sprint assignment, excluding archived items from closed sprints. Returns list and total count.

Instructions

Get TRUE backlog items - work items with NO board/sprint assignment. Returns { items, total }. NOTE: Items in closed sprints are NOT backlog - they are archived work.

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": "get_backlog"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNoThe project ID (optional if HACKNPLAN_DEFAULT_PROJECT set)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv7.2.0

TDQS

A4/5.0
Behavior3/5

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

The description discloses the return format and exclusion criteria, but without annotations, it lacks disclosure of other behavioral traits such as being read-only, authentication requirements, or rate limits. It does not contradict any annotations.

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 extremely concise with two main sentences and a note, conveying all essential information without any unnecessary words or repetition.

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 tool with one optional parameter and no output schema, the description adequately covers the return structure and key constraints. It could be enhanced by mentioning potential pagination or ordering, but it is largely complete.

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?

The input schema has 100% coverage with a description for projectId. The tool description does not add any additional meaning or usage details beyond what the schema provides, so the baseline score applies.

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 clearly defines the tool's purpose: getting true backlog items (no board/sprint assignment), and distinguishes it from other tools by specifying what qualifies as backlog and what does not (closed sprint items are archived).

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 provides implicit guidance on when to use this tool (for unassigned items) and includes a note to avoid misuse by clarifying that closed sprint items are not backlog. However, it does not explicitly name alternative tools or state when not to use it.

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