EduBase MCP Server

Official

by EduBase

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

edubase_get_quiz_results_user

Read-onlyIdempotent

Retrieve a user's quiz play results, including timestamps, points, validity, and pass/fail status for each attempt.

Instructions

List the results (plays) of a user in a Quiz set, with times, points, validity and whether they passed the grading. Use edubase_get_quiz_results_play for the per-question details of a play.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`quiz`	Yes	Quiz set 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.

Changed10 schema fields changedv2.0.0Sep 15, 2026
- 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": {
+          "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",
+          "valid",
+          "successful"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is covered. The description adds context about what data is returned (times, points, validity, pass status), though it does not disclose other behavioral aspects such as pagination or filtering. Given the strong annotation coverage, this is adequate but not exceptional.

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 concise sentences. The first sentence states the action and scope, and the second provides useful sibling routing. There is no redundant or filler content.

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?

This is a low-complexity read tool with only two fully documented parameters, a rich annotation set, and an output schema. The description clearly identifies what the tool returns and points to the correct sibling for more detailed data, making it complete for an agent to select and invoke 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?

The input schema has 100% description coverage for both parameters ('Quiz set identification string' and 'user identification string'). The description does not add additional meaning beyond the schema, so the baseline score of 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 uses a specific verb ('List') with a clear resource ('results (plays) of a user in a Quiz set') and enumerates the included data: times, points, validity, and pass/fail grading. It also differentiates itself from edubase_get_quiz_results_play by pointing out that this tool handles summary results rather than per-question details.

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 description explicitly tells the agent when to use the sibling tool instead: 'Use edubase_get_quiz_results_play for the per-question details of a play.' This gives clear routing guidance and implies that this tool is for the overall play-level results.

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

Deploy Server