Skip to main content
Glama
Sign In
hacknplan-mcp

hacknplan-mcp

by mtuska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_milestone_metrics

Retrieve burndown and completion metrics for a milestone in HacknPlan by supplying project and milestone IDs.

Instructions

Get a milestone's metrics (burndown / completion).

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>",
      "milestone_id": "<milestone_id>"
    },
    "name": "get_milestone_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
milestone_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. The verb 'Get' implies a read-only operation, but the description does not mention side effects, return format, permission requirements, or any other behavioral detail. It is minimal and leaves many assumptions unstated.

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 with no filler. It conveys the tool's purpose efficiently and wastes no words.

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 metric-reading tool with two integer parameters and no output schema, the description provides the metric categories (burndown/completion) but lacks details about return structure, error cases, or authentication. It is minimally viable but leaves gaps an agent must infer.

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?

Schema description coverage is 0%, and the description does not explain the parameters. While project_id and milestone_id are somewhat self-explanatory, the description adds no semantic detail about how to obtain them, their relationship, or any constraints beyond the schema's integer type and required flags.

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 uses a specific verb ('Get') and resource ('milestone's metrics'), with parenthetical scope ('burndown / completion') that clarifies what kind of metrics. This clearly differentiates it from sibling metric tools like get_project_metrics, get_board_metrics, and get_design_element_metrics.

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

Usage Guidelines3/5

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

The description implies when to use it (whenever milestone-level burndown or completion metrics are needed) but does not explicitly contrast with sibling metric tools or state when not to use it. No alternatives or exclusions are mentioned.

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