Skip to main content
Glama

mystudent_overview

Read-only

Show your MyStudent dashboard to check contact details, study plan, class registrations, fees, tasks, today's calendar, and forms. Use for enrolment, fees, tasks, forms, or student-record questions.

Instructions

Show the MyStudent dashboard (JCU's student administration portal): your contact details, study plan, class registrations, outstanding payments, tasks to complete, today's calendar, and forms in progress or available. Use when the user asks about their enrolment, fees, tasks or forms in MyStudent, or their student record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mystudent_overview"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful scope information by disclosing that the response includes sensitive personal data (contact details, outstanding payments), but it never mentions that a MyStudent session/login may be required even though mystudent_login and mystudent_status exist as siblings.

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 tight sentences, front-loaded with the identity of the tool before the usage triggers. The content enumeration is long but each item carries information an agent needs to judge relevance; minimal waste.

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?

With no output schema, the description usefully serves as a stand-in by listing the sections returned. For a zero-required-parameter read-only dashboard tool this is nearly complete, with the only real omission being session/auth preconditions.

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 description coverage is 100% and the single 'account' parameter is fully documented in the schema, including the pointer to learnjcu_list_accounts. The description adds nothing about the parameter, which is acceptable at this coverage level but earns only the baseline.

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 concrete verb and resource ('Show the MyStudent dashboard') and enumerates the data it surfaces: contact details, study plan, class registrations, payments, tasks, calendar, forms. It is clearly distinguishable from login/status siblings, but it never names an overlapping sibling such as mystudent_study_plan, so an agent must infer where the boundary lies.

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?

The second sentence gives explicit triggers: user asks about enrolment, fees, tasks or forms in MyStudent, or their student record. There is no when-not guidance and no routing to the more focused siblings (mystudent_study_plan, mystudent_page) when the user wants only one section.

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