Skip to main content
Glama
Sign In
hacknplan-mcp

hacknplan-mcp

by mtuska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_project

Retrieves a project with its stages, categories, importance levels, and boards to provide the structural overview needed before creating work items.

Instructions

Get one project with its stages, categories, importance levels and boards rolled up — the structural overview you need before creating work items.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It indicates a read-only retrieval by using 'Get' and describes the returned contents (stages, categories, etc.), but does not mention permissions, error behavior, or any special side effects. This is acceptable for a simple fetch tool.

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, front-loaded sentence that efficiently conveys the tool's action, scope, and usage context. No wasted words.

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 simple get-by-id tool with one parameter, the description is fairly complete. It lists the included related entities and gives usage context. It could mention the return structure in more detail, but the provided information is sufficient for the tool's simplicity.

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

Parameters2/5

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

The schema has 0% description coverage, so the description must compensate. It does not mention project_id or its role, relying on the tool name and schema. Since there is only one obvious parameter, the gap is minor, but the description still adds no explicit value beyond the parameter name.

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 gets a single project along with its stages, categories, importance levels, and boards. It distinguishes itself from list_projects by emphasizing the rolled-up structural overview, which is unique to this tool.

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 clear context, stating that the tool is the 'structural overview you need before creating work items.' This implies when to use it, though it does not explicitly name alternatives or exclusions.

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