Skip to main content
Glama

learnjcu_list_accounts

Read-only

Lists saved University accounts and shows which account is selected for the current session, helping users confirm or choose the account to use.

Instructions

List the saved University accounts (each has its own sign-in) and which one is chosen for this session. Use when the user asks which accounts are saved, or before asking them which account to use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already establish that this is a read-only, closed-world operation. The description adds useful behavioral context by explaining that the result includes saved accounts, each with its own sign-in, and the currently chosen session account. It does not describe the exact response shape, but the tool is simple and the annotations cover its safety profile.

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?

The description is two compact sentences with the core purpose front-loaded. Every clause adds useful context about the account list or when to call it.

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 zero-parameter read-only listing tool with full schema coverage and no output schema, the description gives enough context to understand what it returns conceptually and when to invoke it. It could be slightly richer about the return format, but no critical information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no parameter semantics to document. The description appropriately focuses on what the account listing represents rather than inventing parameter details.

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 and resource: list saved University accounts. It also clarifies the tool's scope by noting that the list includes each account's own sign-in and which account is chosen for the current session, which distinguishes it from account selection or login tools.

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?

It gives clear when-to-use guidance: when the user asks which accounts are saved, or before asking which account to use. It does not explicitly name learnjcu_select_account as the alternative for switching accounts, but the intended sequencing around account choice is clear.

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