Skip to main content
Glama

get_deadlines

Retrieve upcoming and past assignment, exercise, agenda, teleconference, and personal deadlines across Open eClass courses within a chosen time window.

Instructions

Upcoming calendar events for all courses: assignment and exercise deadlines, agenda entries, teleconferences and personal events. Looks days ahead and past_days back from now.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
courseNo
past_daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the two genuinely behavioral facts: results span all courses and the window extends both forward (`days`) and backward (`past_days`). It says nothing about authorization, result ordering, how deadlines are grouped or deduplicated, or how empty windows behave, which are the remaining gaps for an unannotated read tool.

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?

Three short sentences with zero filler: scope and event types first, temporal window second. Every clause contributes information an agent cannot get from the bare schema.

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

Completeness3/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 need not be described, and the temporal semantics are handled well. However, for a 0%-coverage, three-parameter tool with no annotations, leaving `course` unexplained and giving no hint about ordering or result grouping leaves the definition short of what an agent needs to call it with confidence.

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 0%, so the description must compensate, and it does explain `days` (how far ahead) and `past_days` (how far back) in plain terms. The third parameter, `course`, is never addressed — worse, 'for all courses' reads as if no course filter exists, creating mild tension with the schema. Two of three parameters are covered with real meaning.

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?

States a specific resource (upcoming calendar events) and enumerates the event types it returns: assignment and exercise deadlines, agenda entries, teleconferences, personal events. That makes the tool's scope concrete. It stops short of explicitly contrasting itself with siblings like get_assignments or get_exercises, so the agent must infer that this is the aggregated calendar view rather than the per-item listings.

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 'all courses' scope plus the mixed event types suggest this is the tool for a consolidated time-window view, and the days/past_days sentence implies it is time-scoped. There is no explicit when-to-use statement, no named alternative, and no guidance on when a per-item tool such as get_assignments would be preferable.

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