Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_post_user_assume

Assume a user identity for EduBase requests by providing credentials to obtain an assume token, enabling subsequent actions to be performed as that user.

Instructions

Assume user for next requests with assume token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesuser identification string, username or email address
passwordNopassword or user secret

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesuser identification string
tokenYesassume token
validYesvalidity of the generated token

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.2.5
    • changedOutput schema / properties / token / type
      Previous value: -"boolean"New value: +"string"
  2. Changed2 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "token": {
+      "description": "assume token",
+      "type": "boolean"
+    },
+    "user": {
+      "description": "user identification string",
+      "type": "string"
+    },
+    "valid": {
+      "description": "validity of the generated token",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user",
+    "token",
+    "valid"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already indicate mutability (readOnlyHint false) and non-destructive nature. Description adds the concept of 'assume token' but does not explain behavior like token lifecycle, session scope, or auth requirements. No contradiction with annotations.

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?

Description is extremely concise (one sentence) with no waste. However, it may be too brief, missing important context like when to use or what the output is.

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

Completeness2/5

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

The description fails to explain the side effect (e.g., subsequent requests are as the assumed user), the role of the token, or the lifecycle. Sibling tool edubase_delete_user_assume suggests a need for cleanup, which is not mentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters (user, password) are described in the schema. The description adds no extra meaning beyond what the schema provides, such as format or constraints.

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 clearly states the tool assumes a user for subsequent requests using an assume token. It distinguishes from sibling tools like edubase_delete_user_assume and edubase_post_user_login by focusing on the assumption action. However, the term 'assume token' is ambiguous and lacks explanation.

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 on when to use this tool versus alternatives like edubase_post_user_login or when to end the assumption (edubase_delete_user_assume). Prerequisites and consequences are not mentioned.

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/EduBase/MCP'

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