Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_user_login

Generate a login link for a user, directing them to an exam or custom redirect after authentication. Configurable expiry and usage limits, and reuses existing matching links to avoid duplicates.

Instructions

Generate login link. If a valid link with the same settings exists, it will be returned instead of creating a new one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examNothe exam identification string to redirect the user to (mutually exclusive with redirect)
userYesuser identification string
shortNogenerate shortened (eduba.se) link (only if feature is enabled on EduBase) (default: false)
loginsNototal count the link can be used to login users (default: 1)
expiresNoexpiry in days (1-30) or YYYY-MM-DD (default: 1 day)
redirectNoredirect after a successful login (URI path or [{content_type}:{tag}])
templateNoa template ID for the login link

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
userYes
countYes
validYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / count / description
      Removed value: -"maximum number the link can be used to login"
    • removedOutput schema / properties / url / description
      Removed value: -"the login link"
    • removedOutput schema / properties / user / description
      Removed value: -"the user identification string"
    • removedOutput schema / properties / valid / description
      Removed value: -"validity of the generated link"
  2. Changed8 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / exam
      Added value: +{
+  "description": "the exam identification string to redirect the user to (mutually exclusive with redirect)",
+  "type": "string"
+}
    • addedInput schema / properties / expires / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / expires / type
      Removed value: -"string"
    • addedInput schema / properties / logins / maximum
      Added value: +255
    • addedInput schema / properties / logins / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / logins / type
      Previous value: -"number"New value: +"integer"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "maximum number the link can be used to login",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "url": {
+      "description": "the login link",
+      "format": "uri",
+      "type": "string"
+    },
+    "user": {
+      "description": "the user identification string",
+      "type": "string"
+    },
+    "valid": {
+      "description": "validity of the generated link",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user",
+    "url",
+    "valid",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A3.8/5.0
Behavior4/5

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

The description discloses a key behavioral trait beyond the annotations: if a valid link with the same settings exists, it is returned instead of creating a new one. This is consistent with readOnlyHint=false and does not contradict idempotentHint=false because the deduplication is conditional. It does not explain permissions or side effects, but annotations already cover the basic safety profile.

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 two short sentences with no filler. The main purpose is front-loaded, and the second sentence adds meaningful behavioral information about link reuse rather than repeating schema or annotation content.

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?

Given full parameter documentation, an output schema, and available annotations, the description covers the core behavior and the important deduplication nuance. The main gap is the lack of explicit guidance about choosing this tool over sibling login-related endpoints, but that is more of a usage-guideline concern.

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 description coverage is 100%, so the input schema fully documents all parameters. The description adds no direct parameter-level detail, though the phrase 'same settings' hints that the combination of parameters determines link uniqueness. This meets the baseline for a schema-covered tool.

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 states a specific action and resource: generate a login link, and the second sentence adds a useful distinction by describing the reuse of existing valid links. It does not explicitly differentiate this from sibling tools like edubase_get_user_login or edubase_post_exam_autologin, so it falls short of a full 5.

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?

The intended use case is implied: call this when a login link for a user is needed. However, there is no explicit when-to-use versus alternative tools, and no mention of sibling operations like edubase_get_user_login or edubase_delete_user_login, so guidance is only implicit.

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