Skip to main content
Glama

get_user_workload

Read-onlyIdempotent

Retrieves a user's workload across open projects, showing open and overdue task counts per project and board, plus a task list with overdue items first and optional completed tasks.

Instructions

What one person (name/id/"me") has on their plate across all open projects: open task count, overdue, per project and per board, plus the task list (overdue first). Done tasks only if include_done.

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": {
      "user": "<user>"
    },
    "name": "get_user_workload"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYes
include_doneNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/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 real behavioral context beyond that: scope is limited to open projects, results are ordered overdue-first, and completed tasks are excluded by default unless include_done is set. It doesn't disclose list size limits or pagination of the task list, which keeps it from a 5.

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?

It is a single dense passage with the scope (one person, all open projects) front-loaded, followed by what is returned and the one behavioral toggle. The telegraphic style compresses well but borders on run-on; every clause still carries information.

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?

An output schema exists so return structure needn't be spelled out, and the description still previews the shape of the result usefully. For a two-parameter read tool this covers scope, ordering, and defaults adequately; only result-size or pagination behavior is unaddressed.

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?

Schema coverage is 0% and both parameters are bare types, so the description carries the burden. It explains that user accepts a name, an id, or the literal "me", and that include_done governs whether completed tasks appear at all, which is meaningful semantics the schema does not convey. Default value for include_done is only implied via 'only if'.

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 names a specific resource (a single person's workload: open task count, overdue count, per-project and per-board breakdown, plus the task list) rather than restating the tool name. It implicitly separates itself from counting tools like get_task_counts by promising both aggregates and the underlying list. It never names a sibling explicitly, so differentiation is by scope description alone.

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 implied rather than stated: an agent can infer this is the tool for 'how busy is person X' questions. There is no explicit when-not guidance or named alternative for cases like 'just my tasks' (list_my_tasks) or workspace-wide counts. The include_done clause is the only conditional guidance offered.

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