Skip to main content
Glama

learnjcu_select_account

Read-only

Selects which saved account all other tools use for the current session. Call it after the user names an account so grades, subjects, and submissions target the right login.

Instructions

Choose which saved account the other tools use for the rest of this session. Call it after the user has said which account they mean; never pick one for them.

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": {
      "account": "<account>"
    },
    "name": "learnjcu_select_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesA saved account name from learnjcu_list_accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, it discloses the key behavioral trait: the selection persists for the rest of the session and governs all other tools. That is valuable context a readOnlyHint alone would not convey (the tool alters agent session state even though it reads no external data). It does not say what happens with an unknown account name or whether the choice survives reconnect.

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 effect, followed by the call condition and the constraint. Every clause carries information and nothing is padded.

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-parameter, no-output-schema tool with annotations present, the description covers purpose, timing, and the anti-guessing constraint. Only edge-case behavior (invalid or stale account name, session expiry) is left unstated, which is a minor omission at this complexity.

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 parameter description already specifies that the value is a saved account name from learnjcu_list_accounts. The description reinforces that the value must originate from the user rather than the agent, but adds no format or validation detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Choose'), the resource ('which saved account'), and the effect scope ('the other tools use for the rest of this session'). An agent can immediately distinguish this session-configuration tool from data-fetching siblings like learnjcu_list_accounts or learnjcu_api_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit timing ('Call it after the user has said which account they mean') and an explicit prohibition ('never pick one for them'). The only minor gap is that it doesn't name learnjcu_list_accounts as the discovery step, though the schema's parameter description already does that.

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