Skip to main content
Glama

upcoming_deadlines

Retrieve assignments due within a specified number of days, sorted by soonest deadline and shown in your configured timezone.

Instructions

Assignments due within the next days days, soonest first, times in the configured timezone.

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": "upcoming_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose ordering ('soonest first') and timezone semantics, which are genuinely useful behavioral facts. However, it leaves a meaningful ambiguity: whether already-overdue or undated assignments are included in the window, and there is no note on result size or limits.

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 tight sentence with the core predicate front-loaded, followed by the two behavioral qualifiers (ordering, timezone). No wasted words.

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 values need not be explained, and with one optional parameter the definition is nearly sufficient. The remaining gap is the treatment of overdue items and window boundaries, which matters for an agent deciding whether this call is enough.

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 description coverage is 0%, so the description must compensate, and it does: 'within the next `days` days' defines exactly what the single parameter means. It does not restate the default of 14, but the semantic meaning is fully conveyed.

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 states a specific verb and resource ('Assignments due within the next `days` days') with clear scope, and the sort order ('soonest first') and timezone handling are stated. It implicitly distinguishes itself from list_assignments by adding a due-window filter, though it never names that sibling.

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?

The use case (deadline triage within a horizon) is strongly implied by the wording, but there is no explicit when-to-use / when-not guidance and no reference to list_assignments as the unfiltered alternative. An agent can infer the intent but must guess the boundary between this tool and the general assignment lister.

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