Skip to main content
Glama
Sign In
HacknPlan MCP Server

HacknPlan MCP Server

by Lint111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_importance_levels

Retrieve importance levels for a project to organize tasks by priority, with support for pagination.

Instructions

List importance/priority levels for a project. Returns { items, total, offset, limit, hasMore }.

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_importance_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (default: 50, max: 200)
offsetNoSkip first N items (default: 0)
projectIdNoThe project ID (optional if HACKNPLAN_DEFAULT_PROJECT set)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv7.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden for behavioral disclosure. It implies a read-only operation ('List') and describes the return shape, but omits details like whether authorization is required, if it is safe to call repeatedly, or any potential side effects.

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: one sentence stating purpose and one specifying the return shape. Every sentence is informative and earned its place. No redundant information.

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

Completeness3/5

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

The description covers the basic purpose and pagination format but lacks details on the structure of items (e.g., what fields each importance level object contains). Given the tool's simplicity and lack of output schema, the description is minimally adequate but could be more 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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description does not add meaning beyond the schema; it mentions 'for a project' but does not elaborate on the projectId parameter's purpose or the optional default project environment variable.

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 states the tool lists importance/priority levels for a project, using a specific verb 'List' and resource 'importance/priority levels'. This distinguishes it from sibling list tools for other entities like work items, projects, or milestones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives is provided. The description does not mention when it is appropriate to call this tool, prerequisites, or any exclusions. The agent must infer usage solely from the name.

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