Skip to main content
Glama

learnjcu_my_grades

Read-only

Retrieve a course gradebook showing every assessment with due date, submission status, grade and feedback. Use it to answer questions about a subject's assignments, marks or feedback.

Instructions

Show the gradebook for a course: each assessment with due date, your submission status, grade and feedback. Use when the user asks about a course's assignments, their grades or feedback.

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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 that results are per-assessment records containing due date, status, grade and feedback, which is useful given there is no output schema, but it says nothing about empty gradebooks, unposted grades, or account-scoping behavior.

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?

Two sentences, zero waste: the first describes the tool and its return contents, the second gives the trigger condition. Content is front-loaded and nothing is redundant.

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?

For a two-parameter, read-only lookup with full schema coverage and annotations, the definition is nearly complete — the return shape substitute ('each assessment with due date, submission status, grade and feedback') compensates for the missing output schema. Only sibling disambiguation for grade vs. submission vs. deadline queries is left implicit.

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%, so both parameters are already documented in the schema, including the accepted courseId formats and the account fallback note. The description adds no parameter meaning beyond that, so the 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 and resource ('Show the gradebook for a course') and enumerates the returned content (due date, submission status, grade, feedback). It is far more specific than a tautology, but it does not name a sibling it is distinct from (e.g., learnjcu_list_submissions, learnjcu_upcoming_deadlines), so an agent must infer the boundary itself.

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 an explicit trigger: 'Use when the user asks about a course's assignments, their grades or feedback.' That covers the main when-to-use case clearly, but offers no exclusions or routing advice for the closely related deadline/submission tools.

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