Skip to main content
Glama

get_user

Retrieve authenticated user information and enrolled courses from Ed Discussion to manage academic activity and content.

Instructions

Get authenticated user info and enrolled courses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'get_user' tool is defined here using server.tool, and it calls api.getUser() to fetch data.
    server.tool("get_user", "Get authenticated user info and enrolled courses", {}, async () => {
      try {
        return ok(await api.getUser());
      } catch (err) {
        return fail(err);
      }
    });
  • The actual implementation of getUser() inside the EdApiClient class in src/api.ts.
    async getUser(): Promise<EdUserResponse> {
      return this.request<EdUserResponse>("GET", "user");
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It implies reliance on authentication context (no user ID parameter needed), but lacks disclosure of read-only nature, error cases (e.g., unauthenticated requests), rate limits, or exact return structure.

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?

Single efficient sentence with zero waste. Information is front-loaded and appropriately sized for the tool's simplicity.

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-parameter tool without output schema or annotations, the description minimally suffices by indicating what data is returned (user info plus courses). However, gaps remain regarding return structure, error handling, and behavioral side effects.

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?

Input schema has zero parameters. According to scoring rules, 0 params establishes a baseline of 4. The description implies no arguments are needed, which aligns with the empty schema.

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 uses specific verbs ('Get') and resources ('authenticated user info and enrolled courses'). The term 'authenticated' effectively distinguishes this from sibling 'list_users' by implying the current user context, though it doesn't explicitly contrast with alternatives.

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?

No guidance provided on when to use this versus 'list_users' or other user-related tools. Does not mention prerequisites (e.g., requires active session) or explicit use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rob-9/edstem-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server