Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_class_assignments

Read-onlyIdempotent

Retrieve class assignments with titles, links, statuses, and submission periods. Get a clear overview of pending and active work for any class.

Instructions

List the assignments of a class, with their titles, links, status (INACTIVE, ACTIVE, STARTED, SUBMITTED, GRADED) and submission period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classYesclass identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
assignmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.0
    • removedOutput schema / properties / assignments / items / properties / assignment / description
      Removed value: -"assignment identification string"
    • removedOutput schema / properties / assignments / items / properties / ends / description
      Removed value: -"when the assignment submission ends"
    • removedOutput schema / properties / assignments / items / properties / link / description
      Removed value: -"link to the assignment page"
    • removedOutput schema / properties / assignments / items / properties / starts / description
      Removed value: -"when the assignment submission starts"
    • removedOutput schema / properties / assignments / items / properties / status / description
      Removed value: -"assignment and submission state (INACTIVE, ACTIVE, STARTED, SUBMITTED, GRADED)"
    • removedOutput schema / properties / assignments / items / properties / title / description
      Removed value: -"title of the assignment"
  2. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / assignments / items / properties / name
      Removed value: -{
-  "description": "title of the assignment",
-  "type": "string"
-}
    • addedOutput schema / properties / assignments / items / properties / title
      Added value: +{
+  "description": "title of the assignment",
+  "type": "string"
+}
    • changedOutput schema / properties / assignments / items / required
      Previous value: -[
-  "assignment",
-  "name",
-  "link",
-  "status",
-  "starts",
-  "ends"
-]New value: +[
+  "assignment",
+  "title",
+  "link",
+  "status",
+  "starts",
+  "ends"
+]
  3. Changed2 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "assignments": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "assignment": {
+            "description": "assignment identification string",
+            "type": "string"
+          },
+          "ends": {
+            "description": "when the assignment submission ends",
+            "type": "string"
+          },
+          "link": {
+            "description": "link to the assignment page",
+            "type": "string"
+          },
+          "name": {
+            "description": "title of the assignment",
+            "type": "string"
+          },
+          "starts": {
+            "description": "when the assignment submission starts",
+            "type": "string"
+          },
+          "status": {
+            "description": "assignment and submission state (INACTIVE, ACTIVE, STARTED, SUBMITTED, GRADED)",
+            "enum": [
+              "INACTIVE",
+              "ACTIVE",
+              "STARTED",
+              "SUBMITTED",
+              "GRADED"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "assignment",
+          "name",
+          "link",
+          "status",
+          "starts",
+          "ends"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "assignments"
+  ],
+  "type": "object"
+}
  4. First observedv1.0.22

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, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the status enum and submission period details, which is useful but doesn't disclose pagination, error behavior, or any other behavioral nuance. With annotations covering the core, a 3 is appropriate.

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 with zero wasted words. It states the action and the output fields efficiently, making it easy for an agent to parse.

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?

The tool has an output schema, so return format is handled externally. The description covers the essential purpose and key output fields. It lacks mention of potential edge cases (e.g., empty class) but for a simple read-only list tool, this is adequate.

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?

The only parameter 'class' is fully described in the schema as 'class identification string' (100% coverage). The description does not add further meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb 'List' and resource 'assignments of a class', and enumerates the returned fields (titles, links, status, submission period). It is unambiguous and distinct from sibling tools like get_class_members or get_class.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no indication of when to use this tool versus alternatives, nor any exclusions or prerequisites. It simply states what it does, leaving the agent to infer usage from the name and context.

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

Deploy Server

Other Tools