Skip to main content
Glama

mystudent_status

Read-only

Check whether a saved MyStudent session exists and when it expires; if multiple accounts are saved and none is selected, list them all.

Instructions

Check whether a MyStudent session is saved and when it expires. With several saved accounts and none chosen, it lists them all.

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_status"
  }
}

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.7/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 description's job is to add context, and it does: it discloses the expiry-reporting behavior and the fallback of listing all saved accounts when none is selected. It does not describe output shape or what happens with an invalid account name, keeping it short of a 5.

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, with the primary capability front-loaded and the edge case second. No filler, though the second sentence overlaps with the parameter description in the schema.

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 one-optional-parameter read-only status check with no output schema, the description covers what is checked, what triggers a list response, and what the parameter does. The absence of return-format detail is acceptable since no output schema exists but the described outputs are self-explanatory.

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% and the single optional parameter is fully documented in the schema, including the cross-reference to learnjcu_list_accounts, so the baseline is 3. The description merely reiterates the multi-account condition without adding formatting or resolution details beyond the schema.

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?

The description states a specific verb and resource: it checks whether a MyStudent session is saved and reports its expiry time. That is distinct from login-oriented siblings like mystudent_login, though the description never names an alternative to disambiguate 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 implied rather than stated: an agent can infer this is a pre-flight check before calling mystudent_login or the page tools, and the second sentence explains the ambiguous-account case. However, there is no explicit 'use this when X, use mystudent_login when Y' routing, so the agent must infer the workflow.

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