EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_patch_quiz_grading_preset

Idempotent

Update an existing custom grading preset by replacing its thresholds, grades, title, or language. Use this to adjust scoring criteria for quizzes or exams when the preset is no longer suitable.

Instructions

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

Input Schema

TableJSON 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

Output Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.2/5.0

Behavior4/5

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

Annotations already indicate this is a modifying, idempotent, non-destructive operation. The description adds the meaningful behavioral constraint that global and organization presets are off-limits, which is not evident from the annotations or schema alone.

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, efficient sentence that communicates the core action and the most important restriction. No filler or redundant wording.

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 small update tool with rich schema descriptions, an output schema, and supportive annotations, the description is mostly complete. It covers the main action and scope restriction, though it does not explicitly summarize partial-update semantics beyond what the schema already states.

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 the schema already documents each parameter in detail. The description does not add significant parameter-level meaning beyond establishing that only custom presets are updatable.

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 states a specific verb ('Update'), a specific resource ('existing custom grading preset'), and the key constraint that global and organization presets cannot be modified. This clearly differentiates the tool from siblings like post_quiz_grading_preset and delete_quiz_grading_preset.

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?

The description makes clear this tool is for updating custom presets only and explicitly excludes global and organization presets. It does not explicitly name alternative tools for creation or deletion, but the usage context is still sufficiently clear.

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

Deploy Server