Skip to main content
Glama

studentfirst_status

Read-only

Checks whether a StudentFirst session is saved and, if several accounts exist with none selected, lists all saved accounts for selection.

Instructions

Check whether a StudentFirst session is saved. 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": "studentfirst_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

B3.4/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 safety is covered. The description adds one genuinely useful behavioral detail — that an ambiguous account situation causes it to list all saved accounts rather than fail — but says nothing about session validity, expiry, or what a negative result looks like.

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 short sentences, front-loaded with the core purpose and followed by the one edge-case behavior that matters. Nothing is wasted.

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 single-optional-parameter read tool with annotations covering safety and no output schema, this is close to sufficient. A brief note on what the check returns (e.g. saved/not saved plus account list) would close the remaining gap.

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 coverage is 100% and the account parameter's schema description already states it is only needed when several accounts are saved and none chosen yet. The description's account sentence largely restates that, adding no format, identifier, or selection semantics 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?

States a specific verb and resource: check whether a StudentFirst session is saved. That is clearly distinct from sibling tools like studentfirst_login or studentfirst_overview, though it never explicitly says how it differs from learnjcu_status or mystudent_status.

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?

The second sentence implies a usage scenario (multiple saved accounts, none chosen → it lists them), which helps. But there is no explicit guidance on when to call this versus studentfirst_login or the other *_status tools, so the agent must infer that this is a pre-flight check before login.

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