Skip to main content
Glama

whoami

Verify login and identify which Open eClass account and site are active, confirming read-only access before retrieving courses, announcements, deadlines, assignments, or messages.

Instructions

Check that the login works and see which account and eClass site are in 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": "whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the essential traits: the call validates authentication state and returns identity/context information, implying a read-only, side-effect-free probe. It stops short of saying what happens when the login is invalid (error vs. empty result), which is the one behavioral detail an agent might want.

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?

A single sentence with two tightly linked clauses, front-loading the verification purpose before the returned values. No filler, no repetition of the tool name, nothing that could be cut.

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, no-output-schema tool, the description covers what the agent gets back (account and eClass site), which is the main unknown. It could add a note on failure behavior or on using it as a pre-flight check, but nothing critical for correct invocation 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 zero parameters, so there is nothing for the description to disambiguate; the schema is an empty object and the description correctly implies no inputs are required. Baseline 4 applies for a parameterless tool.

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 names a concrete action pair — validate the login and report the active account and eClass site — which is a distinct diagnostic/identity purpose no sibling (all document/course/message fetchers) shares. It is specific rather than tautological, though it doesn't explicitly label itself as the identity/connectivity tool.

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 implied rather than stated: an agent can infer this is the right call when it needs to confirm credentials work or learn which account/site it is acting as. There is no explicit when-not guidance, no statement about calling it before other operations, and no named alternative.

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