Skip to main content
Glama

get_overdue_tasks

Read-only

Retrieve open tasks with past due dates, optionally scoped to a project, to identify overdue work requiring action.

Instructions

List open tasks whose due date has passed.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoOptional project ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and an output schema exists, so safety and return shape are covered elsewhere. The description adds only the definition of the filter (open AND past due), leaving behavioral questions such as ordering, whether tasks with null due dates are excluded, or pagination unaddressed.

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?

One short sentence, front-loaded with the verb and the exact filtering condition. Nothing redundant and nothing buried.

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?

For a low-complexity, single-optional-parameter read tool with annotations and an output schema, this is nearly sufficient. The minor gap is that 'open' and 'due date has passed' are not operationally pinned down (timezone, null due dates), though the output schema reduces the need for return-value detail.

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 description coverage is 100% and the single project_id parameter is documented in the schema as an optional project filter. The description says nothing about the parameter, so it neither adds nor detracts — the baseline 3 applies.

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 sentence gives a specific verb (List) and a precisely scoped resource (open tasks whose due date has passed), making the filter semantics unambiguous. It does not, however, distinguish itself from siblings like list_tasks or search_tasks, so an agent must infer that this is the overdue-specialized variant.

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 by the definition itself: an agent should reach for this when it wants overdue items rather than all tasks. There is no explicit statement of when to prefer list_tasks or search_tasks, nor any note about scope limitations (e.g., single project vs. all projects).

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