Skip to main content
Glama

Upcoming and overdue

schoology_upcoming
Read-only

Retrieves upcoming assignments with due dates, overdue assignments, and upcoming events across all courses. Use it to see what work is due next in Schoology.

Instructions

Schoology: upcoming assignments with due dates, overdue assignments, and upcoming events across all courses. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

The description restates the read-only annotation ('Read-only') rather than adding to it, and it does disclose the aggregation behavior across all courses, which annotations do not. However, it omits how far ahead 'upcoming' reaches, whether overdue items are time-bounded, and any result-size or pagination behavior — meaningful gaps for a cross-course rollup.

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?

A single front-loaded sentence enumerating exactly what comes back, with no filler. Every clause maps to a distinct content category in the result.

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?

With no input parameters and no output schema, the definition's only real obligation is to say what comes back, which it does. The unresolved definition of 'upcoming' (time window) is the main omission, but it is a minor one for a tool this simple.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline for a parameterless tool 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?

Names the resource set precisely: upcoming assignments with due dates, overdue assignments, and upcoming events, scoped to all courses. The scope and content are unambiguous, though there is no explicit differentiation from the sibling course-listing tools beyond the fact that this aggregates items rather than courses.

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?

'Across all courses' implies this is the unfiltered aggregate view, which is useful routing context, but the definition never says when to prefer it over schoology_courses or schoology_course, nor does it state any prerequisites. Usage is inferable rather than stated.

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