Skip to main content
Glama

learnjcu_whoami

Read-only

Shows the signed-in LearnJCU user and identifies the active saved account, so you can verify which Blackboard identity is currently in use.

Instructions

Show the signed-in LearnJCU user.

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

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.2/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 the safety profile is covered and the description adds no behavioral detail such as whether login is required or what happens when no account is signed in. For a trivial read-only lookup the burden is light, so this is adequate rather than deficient.

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?

A single front-loaded sentence with zero wasted words. It is efficient, though the terseness leaves the return value and login prerequisite unstated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with full schema coverage and no output schema, the definition is mostly sufficient. The notable gap is that it never says what a "user" result contains (username, display name, student ID), which matters for an identity tool an agent may use to confirm session state.

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 account parameter is already well explained (saved account, only needed when several exist, cross-references learnjcu_list_accounts). The description adds nothing beyond the schema, but the baseline of 3 applies when the schema carries the meaning.

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?

"Show the signed-in LearnJCU user" gives a specific verb (Show) and a specific resource (the signed-in user), which is distinguishable from siblings like learnjcu_list_accounts or learnjcu_status. It stops short of naming an alternative, but the identity-lookup purpose is unmistakable.

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

Usage Guidelines2/5

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

The description offers no when-to-use or when-not-to-use guidance and never points at learnjcu_status, learnjcu_list_accounts, or learnjcu_select_account. The only routing hint in the definition lives in the schema's account parameter text, not in the description itself.

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