Skip to main content
Glama

learnjcu_status

Read-only

Check whether a LearnJCU session is saved and when it expires; if several accounts are stored without a selected one, list them for selection.

Instructions

Check whether a LearnJCU 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": "learnjcu_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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds real value by disclosing that the response reports both saved-state and expiry time, and that an ambiguous multi-account state degrades into listing all saved accounts. It does not say what the output looks like beyond that or what happens with an invalid/expired session (e.g. does it error or return null).

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, front-loaded with the primary question (saved? when does it expire?) and followed by the edge-case behavior. No filler or redundant restatement of the tool name.

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 does carry the burden of explaining return content, and it does cover the two key results (saved state, expiry) plus the multi-account branch. For a zero-required-parameter status tool that is nearly complete, though a line about behavior when no session exists would close the remaining gap.

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 cross-reference to learnjcu_list_accounts. The description restates the same optionality condition without adding format, casing, or identifier details beyond the schema, so the baseline of 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?

The description uses a specific verb and resource ("Check whether a LearnJCU session is saved and when it expires"), which clearly identifies the operation. It distinguishes itself from login/select tools by focusing on session status rather than authentication, but it never names a sibling (e.g. learnjcu_whoami or learnjcu_list_accounts) to make the boundary explicit.

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 only implied: call this to learn whether a session is still valid and when it lapses. There is no explicit "use this when... instead of..." guidance, and the fallback-to-listing behavior is described as a side effect rather than as a routing rule telling the agent to prefer learnjcu_list_accounts for enumeration.

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