Skip to main content
Glama

get_project_summary

Retrieves a structured health and diagnostics summary of the project, returning exact task counts and validation warnings for programmatic repository-state verification without Markdown parsing.

Instructions

Retrieves a structured diagnostics and health summary of the project.

Call this tool for automated programmatic verification of repository state health. Returns exact counts and validation warnings without requiring Markdown parsing.

Returns: dict[str, Any]: Diagnostic record containing: - 'goal': Active project goal - 'current_milestone': Current milestone - 'total_decisions': Total recorded ADRs - 'in_progress_tasks': Count of active tasks - 'pending_tasks': Count of queued tasks - 'completed_tasks': Count of finished tasks - 'total_turns': Total recorded chat turns - 'is_healthy': True if zero unowned active tasks and zero unverified completions - 'warnings': List of active governance warnings - 'unowned_active_tasks': List of task IDs missing an assigned owner - 'unverified_completions': List of task IDs completed without notes

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose read-only, side-effect-free retrieval, plus the exact semantics of the computed flag ('is_healthy': True if zero unowned active tasks and zero unverified completions). It does not mention permissions, cost, or rate limits, but for a zero-parameter read this is solid coverage.

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?

The purpose and usage guidance are front-loaded in two tight sentences, but the twelve-item 'Returns' block largely restates the output schema that already exists. Only a few entries (is_healthy, warnings, unowned_active_tasks) add interpretive value beyond the schema's field names.

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?

A zero-parameter read tool with an output schema needs little more than purpose and usage framing, both of which are present. The only redundancy is the verbose return-field listing that the output schema already covers.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description spends its space on output semantics instead, which is appropriate here.

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 opens with a specific verb and resource ('Retrieves a structured diagnostics and health summary of the project') and enumerates the exact metrics returned, so the tool is clearly distinguishable from get_project_board or get_recent_context. It stops short of naming a sibling it is not, which keeps it from a 5.

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?

'Call this tool for automated programmatic verification of repository state health' plus 'without requiring Markdown parsing' gives a concrete usage condition: machine-readable health checks rather than human-facing board/report views. No explicit exclusions or named alternatives are stated, so it falls short of a 5.

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