Skip to main content
Glama

tasks_summary

Read-onlyIdempotent

At-a-glance ticket counts for a project with ZERO rows returned — total plus counts grouped by status, priority, area, and assignee, plus a stale count (in_progress tasks untouched beyond stale_days). It returns a dashboard number ("urgent: 3, high: 28, blocked: 5") instead of listing every task; it scales to thousands of tickets. tasks_list returns the rows themselves.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID (UUID), subdomain, or slug, resolved server-side; 'default' is the organization's shared task board.
stale_daysNoDays without an update after which an in_progress task counts as stale (default 7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, it discloses the critical behavior that ZERO rows are returned, illustrates the aggregate payload ("urgent: 3, high: 28, blocked: 5"), states the grouping dimensions, and defines the stale metric tied to stale_days. This is exactly the context an agent needs to avoid misusing it as a list call.

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?

Front-loads the purpose, then the return shape, then the sibling contrast in three efficient sentences. Minor waste in the doubled "plus ... plus" construction and the emphasis on "ZERO rows returned," but nothing is misleading or padded.

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

Completeness5/5

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

No output schema exists, so the description carries the return-value burden — and it does, with a concrete example payload and the list of grouping dimensions. For a two-parameter read-only aggregate tool, nothing necessary to a correct call is missing.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already documents project_id resolution and the stale_days default of 7. The description restates the stale definition ("in_progress tasks untouched beyond stale_days") but adds no new format or constraint details, so the baseline of 3 applies.

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?

Names a specific resource and output shape ("At-a-glance ticket counts for a project") and immediately contrasts with the sibling that returns rows: "tasks_list returns the rows themselves." An agent can distinguish this from tasks_list without opening either schema.

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?

Gives a clear selection rule: use this when a dashboard number is wanted and the dataset is large ("scales to thousands of tickets"), and names tasks_list for the row-level alternative. It stops short of an explicit exclusion statement such as "do not use when you need per-task fields," so it is strong but not fully prescriptive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources