Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_user_me

Read-onlyIdempotent

Get the current authenticated user's identification, name, account status, and exam account flag to confirm who is making requests.

Instructions

Get the current user the requests are made as: identification string, name, whether the account is enabled and whether it is a generated exam account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYes
nameYes
userYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / exam / description
      Removed value: -"exam (generated) account"
    • removedOutput schema / properties / name / description
      Removed value: -"full name"
    • removedOutput schema / properties / status / description
      Removed value: -"user is enabled"
    • removedOutput schema / properties / user / description
      Removed value: -"user identification string"
  2. Changed3 schema fields changedv1.1.2
    • removedInput schema / properties / user
      Removed value: -{
-  "description": "User identification string.\n- Use 'me' to get the current user.",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "user"
-]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "exam": {
+      "description": "exam (generated) account",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "full name",
+      "type": "string"
+    },
+    "status": {
+      "description": "user is enabled",
+      "type": "boolean"
+    },
+    "user": {
+      "description": "user identification string",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user",
+    "name",
+    "status",
+    "exam"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds valuable context by disclosing that the result is tied to the request's identity and by specifying what data is returned. This goes slightly beyond structured annotations, though it does not discuss authentication prerequisites or error behavior.

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?

The description is a single, front-loaded sentence: 'Get the current user the requests are made as' followed by a concise list of returned fields. Every word earns its place, with no redundant or filler content.

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

Completeness5/5

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

Given the tool's simplicity (zero parameters, clear purpose, comprehensive annotations, and an output schema present), the description is complete. An agent has everything needed to select and invoke the tool correctly, and the output schema covers detailed return structure.

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 has zero parameters, so the baseline is 4. The description accurately describes what the response contains, which is more relevant than parameter semantics here. There is no schema gap for the description to compensate for.

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?

The description uses a specific verb and resource: 'Get the current user the requests are made as', which clearly distinguishes this from siblings like edubase_get_user or edubase_get_users. It also enumerates the exact returned attributes (identification string, name, enabled status, generated exam account), leaving no ambiguity about the tool's purpose.

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?

The phrase 'current user the requests are made as' provides clear context for when to use this tool: when an agent needs information about the authenticated caller's own account, not a queried user. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough that an agent can infer the correct usage without further guidance.

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

Deploy Server

Other Tools