Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_user_login

Read-onlyIdempotent

Retrieve a user's current valid login link and its expiration to verify login status.

Instructions

Get the latest valid login link of a user and its validity. Generate a new link with edubase_post_user_login.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesuser identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
userYes
validYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • 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 (end of day) of the generated link"
  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": {
+    "url": {
+      "description": "the login link",
+      "format": "uri",
+      "type": "string"
+    },
+    "user": {
+      "description": "the user identification string",
+      "type": "string"
+    },
+    "valid": {
+      "description": "validity (end of day) of the generated link",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user",
+    "url",
+    "valid"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A4.3/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, so the safety profile is covered. The description adds useful context: it returns the 'latest valid' link and its validity, which clarifies the result content and the notion of validity. No contradictions 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the purpose, and ends with the alternative. Every word earns its place; no redundancy or filler.

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 low complexity (single parameter, no nested objects), the presence of an output schema (which covers return structure), and annotations covering safety, the description is complete. It states the operation, the result, and the alternative for generation. Nothing critical is missing for an agent to call it correctly.

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% and the parameter 'user' is described as 'user identification string' in the schema. The tool description adds no additional semantics beyond that. With high coverage, the baseline is 3, and the description does not compensate with extra details.

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 'Get' and a clear resource: 'latest valid login link of a user and its validity.' It distinguishes itself from the sibling edubase_post_user_login by explicitly naming the alternative for generating a new link, so an agent can immediately tell what this tool does and what it does not.

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 description states 'Generate a new link with edubase_post_user_login,' which explicitly points to the alternative when a new link is needed. It implies the use case of retrieving an existing link, though it does not explicitly enumerate exclusions or prerequisites. This is clear enough for an agent to decide when to call this tool versus the generation sibling.

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