EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_get_exam_results_user

Read-onlyIdempotent

List a user's attempts for an exam, showing time, points, attempt index, validity, and whether they passed. Use this to review exam performance.

Instructions

List the results (attempts) of a user in an exam, with times, points, attempt index, validity and whether they passed the grading. Use edubase_get_quiz_results_play for the per-question details of an attempt.

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
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv2.0.0Sep 15, 2026
- removedOutput schema / properties / results / items / properties / attempt / description
```
Removed value: -"index of attempt"
```
- removedOutput schema / properties / results / items / properties / play / description
```
Removed value: -"Quiz play identification string"
```
- removedOutput schema / properties / results / items / properties / points_correct / description
```
Removed value: -"total points scored"
```
- removedOutput schema / properties / results / items / properties / points_total / description
```
Removed value: -"total points"
```
- removedOutput schema / properties / results / items / properties / questions_correct / description
```
Removed value: -"number of correctly answered questions"
```
- removedOutput schema / properties / results / items / properties / questions_total / description
```
Removed value: -"total number of questions asked"
```
- removedOutput schema / properties / results / items / properties / successful / description
```
Removed value: -"attempt passed grading threshold (if applicable)"
```
- removedOutput schema / properties / results / items / properties / time_end / description
```
Removed value: -"end time"
```
- removedOutput schema / properties / results / items / properties / time_start / description
```
Removed value: -"start time"
```
- removedOutput schema / properties / results / items / properties / user / description
```
Removed value: -"user identification string"
```
- removedOutput schema / properties / results / items / properties / valid / description
```
Removed value: -"result is valid"
```

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": {
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attempt": {
+            "description": "index of attempt",
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "play": {
+            "description": "Quiz play identification string",
+            "type": "string"
+          },
+          "points_correct": {
+            "description": "total points scored",
+            "type": "number"
+          },
+          "points_total": {
+            "description": "total points",
+            "type": "number"
+          },
+          "questions_correct": {
+            "description": "number of correctly answered questions",
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "questions_total": {
+            "description": "total number of questions asked",
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "successful": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "attempt passed grading threshold (if applicable)"
+          },
+          "time_end": {
+            "description": "end time",
+            "type": "string"
+          },
+          "time_start": {
+            "description": "start time",
+            "type": "string"
+          },
+          "user": {
+            "description": "user identification string",
+            "type": "string"
+          },
+          "valid": {
+            "description": "result is valid",
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "play",
+          "user",
+          "time_start",
+          "time_end",
+          "questions_total",
+          "questions_correct",
+          "points_total",
+          "points_correct",
+          "attempt",
+          "valid",
+          "successful"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context by enumerating exactly what fields the results include (times, points, attempt index, validity, pass status), which helps the agent anticipate the response. It does not mention rate limits or auth, but the annotation coverage lowers the bar.

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, no filler. The main function is front-loaded, and the sibling routing is a separate, clearly marked sentence. Every sentence earns its place.

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?

For a simple, read-only listing tool with two required parameters and an output schema present, the description is complete. It states what the tool returns and how to get more granular data, so an agent has enough context to invoke it correctly. No critical information is missing.

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% with both parameters described as 'identification string,' so the schema already defines the parameters. The description only confirms that 'exam' and 'user' are the identifiers in the context of the tool, adding no format, type, or usage details beyond what the schema provides. Baseline 3 applies.

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 starts with a specific verb ('List') and identifies the exact resource ('results (attempts) of a user in an exam') along with the data elements included ('times, points, attempt index, validity and whether they passed'). It also distinguishes itself from the sibling edubase_get_quiz_results_play by noting that sibling covers per-question details, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives explicit guidance: 'Use edubase_get_quiz_results_play for the per-question details of an attempt.' This tells the agent exactly which sibling to use when deeper detail is needed and implies this tool is for summary-level results. Clear and actionable.

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

Deploy Server