Skip to main content
Glama

get_projects_summary

Read-onlyIdempotent

Summarize task statistics for each project—total, done, open, overdue, due today, and my open/overdue—to provide a current status overview and highlight items needing attention.

Instructions

Per-project task statistics only (fast status overview): total, done, open, overdue, due today, my open/overdue, last completion.

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_projects_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_archivedNo

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?

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds that the call is 'fast' and enumerates the metric fields, which is useful context, but it says nothing about how archived projects are treated, which is the one behavioral choice this tool exposes.

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 dense sentence with the resource and metric list front-loaded and no filler. It is a fragment rather than a full sentence, but nothing in it is wasted.

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?

An output schema exists and annotations cover the safety profile, so return shape and side effects need no explanation. The remaining gap is scope: whether archived projects are included is undocumented in both the schema and the description, which matters for a statistics tool.

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 a single parameter, include_archived, with 0% schema description coverage, and the description never mentions archival at all. The agent is left to guess the default scope of the statistics (active projects only vs. all) from the parameter name alone.

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?

States a specific resource (per-project task statistics) and enumerates the metrics returned (total, done, open, overdue, due today, my open/overdue, last completion), so an agent knows exactly what comes back. The word 'only' implicitly scopes it away from task-level or dashboard-level tools, but it never names sibling get_dashboard_summary or get_task_counts, so differentiation is left to inference.

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?

'fast status overview' implies the use case: a quick per-project rollup rather than detailed task listing. However, no explicit when-to-use versus when-not guidance and no alternative is named, so the agent must infer routing from sibling names alone.

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