Skip to main content
Glama

Who am I

bb_whoami
Read-only

Confirm Blackboard authentication by returning the signed-in user, active API surface, and session health, so you can verify access before using other actions.

Instructions

Return the signed-in Blackboard user, the API surface in use, and session health. Start here to confirm authentication.

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": "bb_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds value the annotations cannot: it enumerates the three categories of information returned (user identity, API surface, session health) and frames the call as an authentication check. It does not discuss error behavior when unauthenticated, which would have completed the picture.

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 with zero filler, and the informational payload is front-loaded before the call-to-action. Every clause adds something an agent would otherwise have to guess.

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 carries the burden of describing returns and does so by naming three concrete pieces of information. It is nearly complete for a trivial zero-param read, though it leaves "session health" unspecified (e.g., expiry, token validity) and says nothing about failures.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema correctly declares an empty object, and the description does not waste words inventing parameter behavior.

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?

"Return the signed-in Blackboard user, the API surface in use, and session health" gives a concrete verb plus three named outputs, so an agent knows exactly what this tool produces. It is distinguishable from data-fetching siblings like bb_get_profile because the scope is the authenticated session, not course or profile data. No sibling is named explicitly, so it stops just short of perfect differentiation.

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?

"Start here to confirm authentication" is an explicit entry-point recommendation that tells the agent when to reach for this tool first. There is no when-not guidance or named alternative, but for a zero-parameter diagnostic tool the use condition is unambiguous.

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