Skip to main content
Glama

Get my profile

bb_get_profile
Read-only

Retrieve your Blackboard profile details—name, username, email, student ID, avatar, and editable fields—to verify account information.

Instructions

Return your profile: name, username, email, student id, avatar and which fields your account may edit.

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

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. The description adds value by disclosing what data is returned, including permission metadata (editable fields), which is beyond the annotation. It does not mention failure modes, but little is needed for a no-arg self-read.

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 the verb and resource first, then the returned fields. No filler; the only slight softness is the vague phrase "which fields your account may edit".

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 explaining return values and does so with a concrete field list. What is missing is minor: it does not state the return format or the identity assumption (always the authenticated user).

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 the baseline is 4; nothing needs compensating. The description correctly avoids inventing parameter discussion.

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?

States a specific verb and resource (return your profile) and enumerates the payload fields, so the agent knows exactly what comes back. It reads as a self-scoped read, distinguishable from bb_update_profile and bb_get_my_grades by the explicit field list.

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?

"Your profile" implies current-user scope with no parameters, and "which fields your account may edit" hints at the update path. However, it never explicitly says to use bb_update_profile to change fields, so the routing to the sibling is only suggested.

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