Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_exam_certificates_user_download

Read-only

Generate a download link for the user's latest exam certificate, returning an existing valid link if one is already available.

Instructions

Generate download link for the latest user exam certificate. If a previous valid link exists, it will be returned instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string
userYesuser identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
playYes
userYes
validYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / play / description
      Removed value: -"Quiz play identification string"
    • removedOutput schema / properties / url / description
      Removed value: -"download link for the certificate"
    • removedOutput schema / properties / user / description
      Removed value: -"user identification string"
    • removedOutput schema / properties / valid / description
      Removed value: -"date of link expiration"
  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": {
+    "play": {
+      "description": "Quiz play identification string",
+      "type": "string"
+    },
+    "url": {
+      "description": "download link for the certificate",
+      "format": "uri",
+      "type": "string"
+    },
+    "user": {
+      "description": "user identification string",
+      "type": "string"
+    },
+    "valid": {
+      "description": "date of link expiration",
+      "type": "string"
+    }
+  },
+  "required": [
+    "play",
+    "user",
+    "url",
+    "valid"
+  ],
+  "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?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds valuable context: it returns a link (not the certificate itself), and it reuses a previous valid link if one exists. This 'latest' and 'reuse existing link' behavior goes beyond what annotations provide. 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.

Conciseness5/5

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

Two sentences, zero waste. The core action is front-loaded, and the important reuse behavior is stated in the second sentence. Every word earns its place.

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?

The tool has an output schema (not shown in detail but indicated as present), so return values are presumably documented there. The description covers the key behavioral nuance (reusing existing links) and the 'latest' scoping. It doesn't mention expiration or validity of the link, but with an output schema present and annotations covering safety, this is reasonably complete.

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 both parameters (exam, user) are documented in the schema as identification strings. The description doesn't add much beyond that, but it does clarify that the link is for the latest certificate for that exam/user combination. Baseline 3 is appropriate since the schema already covers parameter meaning.

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 verb ('Generate download link') and resource ('latest user exam certificate'), which clearly distinguishes it from the sibling get_exam_certificates_user (which likely retrieves certificate data rather than generating a download link). It doesn't explicitly name the sibling, but the action and resource are specific enough.

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 description implies when to use it: when a download link for a user's latest exam certificate is needed. It also notes that a previous valid link will be returned instead, which hints at idempotent-like behavior. However, it doesn't explicitly state when NOT to use it or mention alternatives like get_exam_certificates_user for viewing certificate details.

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