Skip to main content
Glama

Project Dashboard

project_dashboard

Generates a unified project manager dashboard that combines phase state, todo progress, git status, architecture violations, and a health score for quick project oversight.

Instructions

Generate a unified Project Manager Dashboard combining phase state, todo progress, git status, architecture violations, and a project health score.

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": "project_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose that the output is a composite of five named sources, which implies a read-heavy aggregation with no stated side effects. However, 'Generate' is ambiguous about whether anything is written to disk, and nothing is said about cost, latency, or whether the call walks the whole repository. With an output schema present, return shape is not its responsibility, but the mutation/permission ambiguity is a real gap.

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

Conciseness4/5

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

A single front-loaded sentence that leads with the verb and resource and then lists contents, with no filler. It is efficient, though the enumerated contents could be paired with a hint about when to call it rather than being purely a feature list.

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 output schema covers the return value, so the description need not describe fields, and one optional parameter keeps complexity low. What is missing is the meaning of 'path' and any note on whether this is a pure read versus something that materializes a report, which matters for an aggregating tool with no annotations.

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?

There is one parameter, 'path', with 0% schema description coverage and a bare default of '.', and the description never mentions it at all. The agent must guess whether path scopes the repository root, the dashboard output location, or something else. The description should compensate for the coverage gap and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Generate') and a specific resource ('Project Manager Dashboard'), then enumerates the five data sources it aggregates: phase state, todo progress, git status, architecture violations, and health score. That is enough for an agent to distinguish this aggregate view from single-source siblings such as git_status or list_tasks, though it does not explicitly name which siblings overlap.

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?

Usage is only implied: an agent can infer this is the 'give me the whole picture in one call' option, but the description never states when to prefer it over near-neighbours like project_readiness_report, assess_project_readiness, project_info, or next_best_action. No exclusion or prerequisite is provided, so the choice among overlapping reporting tools is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.