Skip to main content
Glama
Sign In
HacknPlan MCP Server

HacknPlan MCP Server

by Lint111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_board

Retrieve details of a specific board by providing its ID. Optionally specify a project ID to scope the request.

Instructions

Get details of a specific board

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": {
      "boardId": "<boardId>"
    },
    "name": "get_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesThe board ID
projectIdNoThe project ID (optional if HACKNPLAN_DEFAULT_PROJECT set)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv7.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. It only implies a read operation by stating 'Get details', but does not explicitly confirm non-destructive behavior, authentication requirements, or what 'details' includes.

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, well-structured sentence of 6 words with no filler. It is appropriately front-loaded and earns its place.

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?

For a simple retrieval tool with two parameters and no output schema, the description is minimally adequate but lacks details on return format, error handling, or any additional context.

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 description coverage is 100%, so the schema already documents both parameters adequately. The description adds no extra meaning beyond what is in 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?

The description clearly states the verb 'Get details' and the resource 'a specific board', which distinguishes it from siblings like 'list_boards' (multiple boards) and 'get_board_metrics' (metrics only).

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 usage guidelines are provided. The description does not mention when to use this tool, prerequisites, or alternatives. The agent is left to infer context from the name alone.

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