Skip to main content
Glama

get_assignments

Retrieves a course's assignments, including deadlines, submission status, and grades, so you can review what is due and how it was evaluated.

Instructions

Assignments of a course with deadline, submission status and grade.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course": "<course>"
    },
    "name": "get_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it only names some returned fields. It says nothing about read-only behavior, whether the caller must be enrolled in or teaching the course, whether grades are included for students, or how large result sets are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence fragment with no wasted words, but it is under-specified rather than concise. The most decision-relevant information for an agent (this is a list operation scoped to one course) is only implicitly present.

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

Completeness2/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 fields need not be explained in detail, but for a tool with one required, undocumented parameter the description should specify the course identifier format and whether results are filtered by user role. Neither is covered, leaving a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter 'course', and the description only echoes 'of a course'. It does not state whether the value is a course ID, a course code, or a name, nor what happens if the course is unknown.

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

Purpose3/5

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

The description identifies the resource and its scope ('Assignments of a course') plus the notable fields returned (deadline, submission status, grade), which lets an agent infer it is a listing tool. However, it is a noun phrase with no verb ('get'/'list'), and it never distinguishes itself from the singular sibling get_assignment or from get_deadlines.

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?

There is no guidance on when to use this tool versus get_assignment (single item) or get_deadlines, both of which overlap in subject matter. The only usage signal is the implicit 'requires a course' framing, leaving the agent to guess at selection criteria.

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