EduBase MCP Server

Official

by EduBase

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

edubase_patch_quiz_grading_preset

Idempotent

Update an existing custom grading preset. The global presets and the presets of the organizations cannot be modified.

Instructions

Update an existing custom grading preset. The global presets and the presets of the organizations cannot be modified.

Input Schema

Name	Required	Description
`type`	No	type of the grading preset, cannot be changed anymore once the preset is used by a Quiz set or an exam
`title`	No	title of the grading preset
`grades`	No	thresholds and grades of the preset, in ascending order, the complete list is replaced
`preset`	Yes	grading preset identification string
`language`	No	language of the grading preset
`successful_all`	No	every grade means success, even the lowest one, only used with the custom type and dropped when the preset is changed to another type, kept unchanged if not specified

Output Schema

Name	Required	Description	Default
`own`	Yes
`type`	Yes
`used`	Yes
`title`	Yes
`grades`	Yes
`preset`	Yes
`language`	Yes
`certificates`	Yes
`configurable`	Yes
`organization`	Yes
`successful_all`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.0.6Oct 14, 2026

addedInput schema / properties / successful_all

Added value: +{
+  "description": "every grade means success, even the lowest one, only used with the custom type and dropped when the preset is changed to another type, kept unchanged if not specified",
+  "type": "boolean"
+}

addedOutput schema / properties / successful_all
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "preset",
-  "title",
-  "type",
-  "language",
-  "configurable",
-  "certificates",
-  "own",
-  "organization",
-  "used",
-  "grades"
-]New value: +[
+  "preset",
+  "title",
+  "type",
+  "language",
+  "configurable",
+  "certificates",
+  "own",
+  "organization",
+  "used",
+  "grades",
+  "successful_all"
+]

Changed12 schema fields changedv2.0.0Sep 15, 2026

removedOutput schema / properties / certificates / description

Removed value: -"the preset decides whether the test was successful, so certificates can be issued with it (see edubase_post_exam_certificates)"

removedOutput schema / properties / configurable / description

Removed value: -"the threshold of the preset can be configured on the Quiz set or the exam"

removedOutput schema / properties / grades / items / properties / grade / description
```
Removed value: -"the grade itself"
```
removedOutput schema / properties / grades / items / properties / text / description
```
Removed value: -"text shown under the grade on the results page (if set)"
```

removedOutput schema / properties / grades / items / properties / threshold / description

Removed value: -"lowest result in percentage the grade is given for, the first item always starts at 0"

removedOutput schema / properties / language / description

Removed value: -"language of the grading preset, null if the preset is available in every language"

removedOutput schema / properties / organization / description

Removed value: -"organization identification string of the preset, null if the preset is not bound to an organization"

removedOutput schema / properties / own / description

Removed value: -"the preset is a custom preset owned by the user"

removedOutput schema / properties / preset / description

Removed value: -"grading preset identification string"

removedOutput schema / properties / title / description
```
Removed value: -"title of the grading preset"
```
removedOutput schema / properties / type / description
```
Removed value: -"type of the grading preset"
```

removedOutput schema / properties / used / description

Removed value: -"the preset is already used by a Quiz set or an exam of the user"

Changed3 schema fields changedv1.2.16Sep 6, 2026

addedOutput schema / properties / certificates

Added value: +{
+  "description": "the preset decides whether the test was successful, so certificates can be issued with it (see edubase_post_exam_certificates)",
+  "type": "boolean"
+}

addedOutput schema / properties / organization

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "organization identification string of the preset, null if the preset is not bound to an organization"
+}

changedOutput schema / required

Previous value: -[
-  "preset",
-  "title",
-  "type",
-  "language",
-  "configurable",
-  "own",
-  "used",
-  "grades"
-]New value: +[
+  "preset",
+  "title",
+  "type",
+  "language",
+  "configurable",
+  "certificates",
+  "own",
+  "organization",
+  "used",
+  "grades"
+]

Addedv1.2.15Sep 2, 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=false, idempotentHint=true and destructiveHint=false, and the title mirrors the description, so the safety profile is covered structurally. The description adds useful scope context by stating which presets are immutable, but does not disclose auth requirements, what happens to existing settings, or the replace semantics of the grades list.

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 short sentences, front-loaded with the action and followed immediately by the scoping constraint. Nothing is redundant and the title/description pairing is consistent.

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?

An output schema exists, so return values need not be described, and the schema fully documents parameters. Annotations carry the safety profile and the description covers the key editability restriction. It would be stronger if it clarified what a patch leaves unchanged versus replaces, but it is adequate for this tool.

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 all six parameters including the nested grades fields are already documented in the schema. The description contributes no additional parameter meaning beyond the reusable-custom-preset restriction, so the baseline 3 is appropriate.

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 and resource ("Update an existing custom grading preset"), so an agent knows exactly what action it performs. It implicitly distinguishes itself from get/post/delete siblings by the "custom" qualifier and the immutability of global/org presets, but it does not name the sibling tools explicitly.

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?

It gives a clear when-not condition: global presets and organization presets cannot be modified, so this tool applies only to custom presets. It stops short of naming the alternative tools for the excluded cases, but the boundary is explicit 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