Skip to main content
Glama
Sign In
HacknPlan MCP

HacknPlan MCP

by jompereira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_milestone_metrics

Retrieve progress and burndown metrics for a milestone to track development velocity and remaining work.

Instructions

Get progress and burndown metrics for a milestone

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": {
      "projectId": "<projectId>",
      "milestoneId": "<milestoneId>"
    },
    "name": "get_milestone_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
milestoneIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided; description does not disclose behavioral details such as read-only nature, auth requirements, or output format. Only implies read operation via 'get'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no waste, but it sacrifices necessary detail for brevity. Could be improved by adding parameter explanations and usage notes.

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

Completeness2/5

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

For a simple tool with 2 params and no output schema, the description fails to explain return structure or usage context. Incomplete for agent decision-making.

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

Parameters1/5

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

Schema description coverage is 0%. Description does not explain the purpose or format of projectId or milestoneId, leaving parameters completely opaque.

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?

Clearly states verb 'get', resource 'milestone metrics', and specific metrics types 'progress and burndown'. Distinguishes from sibling tools like get_milestone.

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 versus alternatives (e.g., get_milestone, get_project_metrics). Lacks context for appropriate scenarios.

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