Skip to main content
Glama

get_assignment

Retrieve a course assignment's details, including description, attachments, deadline, and your own submission if available, to review requirements and track completion.

Instructions

Details of one assignment: description, attached files, deadline, and the student's own submission if there is one.

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>",
      "assignment_id": "<assignment_id>"
    },
    "name": "get_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes
assignment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose that the submission returned is "the student's own" (per-student scoping) and that files/deadline are included, but says nothing about permissions, what happens when the assignment does not exist, or the fact that submission is optional in a structured way.

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 well-formed sentence with the resource front-loaded and the returned fields enumerated; no wasted 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?

Since there is no output schema, describing returned fields is the right move and it is done reasonably. But for a tool whose required parameters are entirely undocumented, the definition should say something about the identifier formats or error/not-found behavior.

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% and the description adds nothing about the two required parameters. It never clarifies whether "course" is an ID, name, or code, or what assignment_id refers to relative to that course.

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 a specific verb+resource ("Details of one assignment") and enumerates what comes back: description, attached files, deadline, and the student's own submission. The singular "one assignment" implicitly separates it from the plural listing siblings, but no sibling is named explicitly.

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: fetch this when you need the full detail of a single assignment. There is no explicit guidance on when to prefer it over get_assignments or get_deadlines, and no stated prerequisites (e.g., enrollment).

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