EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_get_exam_certificates_user

Read-onlyIdempotent

Retrieve certificate details for a specific exam and user. Provide exam and user identifiers to get the latest certificate information.

Instructions

Get (the latest) certificate details for a specific exam and user.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`exam`	Yes	exam identification string
`user`	Yes	user identification string

Output Schema

TableJSON Schema

Name	Required	Description	Default
`play`	Yes
`user`	Yes
`serial`	No
`expires`	No
`archived`	Yes
`eligible`	Yes
`certified`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv2.0.0Sep 15, 2026

removedOutput schema / properties / archived / description
```
Removed value: -"exam result is archived"
```

removedOutput schema / properties / certified / description

Removed value: -"result is eligible for certification and also certified"

removedOutput schema / properties / eligible / description
```
Removed value: -"result is eligible for certification"
```

removedOutput schema / properties / expires / description

Removed value: -"date of expiration, only present if the result is certified and expiration is configured"

removedOutput schema / properties / play / description
```
Removed value: -"Quiz play identification string"
```

removedOutput schema / properties / serial / description

Removed value: -"serial number of the certificate, only present if the result is certified and serial numbering is enabled"

removedOutput schema / properties / user / description
```
Removed value: -"user identification string"
```

Changed2 schema fields changedv1.1.2Mar 13, 2026

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": {
+    "archived": {
+      "description": "exam result is archived",
+      "type": "boolean"
+    },
+    "certified": {
+      "description": "result is eligible for certification and also certified",
+      "type": "boolean"
+    },
+    "eligible": {
+      "description": "result is eligible for certification",
+      "type": "boolean"
+    },
+    "expires": {
+      "description": "date of expiration, only present if the result is certified and expiration is configured",
+      "type": "string"
+    },
+    "play": {
+      "description": "Quiz play identification string",
+      "type": "string"
+    },
+    "serial": {
+      "description": "serial number of the certificate, only present if the result is certified and serial numbering is enabled",
+      "type": "string"
+    },
+    "user": {
+      "description": "user identification string",
+      "type": "string"
+    }
+  },
+  "required": [
+    "play",
+    "user",
+    "archived",
+    "eligible",
+    "certified"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

TDQS

A3.8/5.0

Behavior3/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 only the 'latest' behavioral nuance; it does not describe not-found behavior or what 'certificate details' contains, but the output schema helps fill that gap.

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 sentence with no filler. The verb and resource are front-loaded, and the parenthetical 'latest' adds meaningful nuance without bloating the text.

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?

For a simple read operation with complete parameter schemas, an output schema, and safety-related annotations, the description is nearly sufficient. The only notable omission is an explicit pointer to sibling tools for other certificate operations, but the 'specific exam and user' wording makes the intended use clear.

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 'exam' and 'user' are already documented as identification strings. The description simply restates that they identify the exam and user, adding no extra semantic detail beyond the schema.

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 clearly states the operation ('get certificate details'), the scope ('for a specific exam and user'), and adds the nuance 'latest'. It is easily distinguishable from siblings like edubase_get_exam_certificates (which appears to be the collection-level variant) and edubase_post_exam_certificates_user_download (a download action).

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 you need the latest certificate details for one particular exam/user. However, it does not explicitly tell the agent to prefer other tools for retrieving all certificates or downloading certificates, leaving some sibling discrimination to inference.

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

Deploy Server