Skip to main content
Glama

get_task_counts

Read-onlyIdempotent

Retrieve your due-today and total open task counts for the current workspace, so agents can check workload and prioritize tasks quickly.

Instructions

My task badge counts in this workspace: due today and total open.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds real value by defining the two counts returned (due today, total open) and scoping them to the caller's own tasks in the current workspace. It says nothing about how 'due today' is computed (timezone/date boundary) or whether counts include completed or archived tasks, which is the remaining behavioral gap.

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

Conciseness5/5

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

A single sentence, front-loaded with the resource and followed by the two metrics. No filler, no redundancy, and the scope qualifiers are compactly bundled.

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?

With zero parameters, a rich annotation set and an output schema, the description need only say what is counted and for whom—which it does. The only omission is the definitional edge cases (completed tasks, date boundary), which an agent might need to interpret the numbers correctly.

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 zero parameters, so the schema carries no semantics burden and the baseline of 4 applies. The description correctly signals that scoping is implicit (caller identity and current workspace) rather than parameterized.

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?

Names a specific resource (task badge counts) and enumerates exactly which metrics are returned: due today and total open. It also scopes the result to 'my' tasks in 'this workspace', which distinguishes it from list_tasks. It stops short of naming a sibling such as list_my_tasks or get_dashboard_summary for differentiation.

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: the phrase 'badge counts' suggests a lightweight summary is wanted rather than a full task list, but the description never says when to prefer this over list_my_tasks or get_dashboard_summary. No exclusions or preconditions are stated.

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