Skip to main content
Glama

learnjcu_list_submissions

Read-only

View an assignment's submission settings (due date, attempts allowed, file or text) and every attempt made, newest first, before submitting or checking what was already submitted.

Instructions

Show a LearnJCU assignment's submission settings (due date, attempts allowed, file/text allowed) and every attempt you have made, newest first, with status, receipt and files. Use when the user asks for an assignment's details (due date, attempts left, what can be submitted) or what they have already submitted, and before submitting.

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": {
      "courseId": "<courseId>",
      "assignment": "<assignment>"
    },
    "name": "learnjcu_list_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.
courseIdYesCourse primary id like "_123456_1" (from learnjcu_list_courses), a subject code like "BU2001", or the full course code
assignmentYesA unique part of the assignment title (e.g. "CW2"), or its content or gradebook column id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds value by specifying result ordering ('newest first') and the shape of each attempt record (status, receipt, files). It does not discuss account-selection behavior when multiple accounts exist, which is left to the schema.

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?

Two sentences, front-loaded with what is returned and followed by when to use it. The parenthetical field lists are dense but each item is informative; no filler sentences.

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?

There is no output schema, so the description usefully enumerates the returned data, and the usage sentence covers the decision context. Completeness is slightly reduced by not addressing multi-account behavior or whether 'every attempt' is paginated.

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 100% with rich per-parameter descriptions (course id formats, 'a unique part of the assignment title'), so the schema carries the semantics. The description adds little parameter-level meaning beyond implying the assignment argument identifies one assignment; baseline 3 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?

States a specific verb ('Show') and a clearly bounded resource: an assignment's submission settings plus the caller's own attempts, with the returned fields enumerated (due date, attempts allowed, file/text allowed, status, receipt, files). An agent can distinguish this from a plain grades or deadlines listing. It does not name a sibling explicitly, so it stops short of the top band.

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

Usage Guidelines4/5

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

Gives concrete triggering conditions ('when the user asks for an assignment's details... or what they have already submitted') and a sequencing rule ('before submitting'), which implicitly routes to the submit tool. No when-not guidance or explicit alternative naming is provided.

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