Skip to main content
Glama

Get upcoming work across courses

bb_get_upcoming_work
Read-only

Get assignments due soon and recently overdue across courses, including submission status and undated counts. Use it to prioritize deadlines and spot work needing attention.

Instructions

Assignments due soon across courses, submission status, recently overdue items and undated counts. Default seven days ahead through end of the last day in Asia/Dubai, plus three days overdue. Unknown submission status never means confirmed missing work.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
courseIdNoOmit to check up to 20 available courses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the read-only and closed-world annotations, the description adds meaningful behavior: the default seven-day forward window ends at the last day in Asia/Dubai, three overdue days are included, and unknown submission status must not be treated as confirmed missing work. It does not explain return shape or whether results are grouped, but the timezone and status caveats are valuable.

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?

The description is compact and front-loads the main scope. The first sentence is a list-like fragment and the second is dense, but there is no redundant wording.

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?

For a cross-course aggregation tool with no output schema, the description covers what is included and the default time boundary. It leaves out return structure and grouping, and does not fully explain parameter interactions, so it is adequate but incomplete.

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 coverage is 50%, and the description compensates partly for the undocumented days parameter by giving a default seven-day forward window plus three overdue days and a timezone boundary. It does not clarify how an explicit days value interacts with the overdue window, and courseId semantics remain solely in the schema.

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 specifies the resource and scope: assignments due soon across courses, submission status, overdue items, and undated counts. This distinguishes it from single-item siblings like bb_get_assignment or bb_get_assessment, though it uses a noun phrase rather than an explicit verb.

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 scope: retrieve upcoming work across courses. However, the description does not explicitly say when to choose this tool over alternatives such as bb_get_recent_updates or bb_get_assignment_context, nor does it state exclusions.

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