Skip to main content
Glama
Sign In
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_quiz_grading_preset

Read-onlyIdempotent

Get a grading preset with its thresholds and grades, including whether its threshold is configurable and whether certificates can be issued with it. List the presets with edubase_get_quiz_grading_presets.

Instructions

Get a grading preset with its thresholds and grades, including whether its threshold is configurable and whether certificates can be issued with it. List the presets with edubase_get_quiz_grading_presets.

Input Schema

NameRequiredDescriptionDefault
presetYesgrading preset identification string

Output Schema

NameRequiredDescriptionDefault
ownYes
typeYes
usedYes
titleYes
gradesYes
presetYes
languageYes
certificatesYes
configurableYes
organizationYes
successful_allYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.6
    • 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"
+]
  2. Changed12 schema fields changedv2.0.0
    • 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"
  3. Changed3 schema fields changedv1.2.16
    • 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"
+]
  4. Addedv1.2.15

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's added detail is mostly about returned content, which the output schema already documents, so behavioral value beyond structured data is limited.

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 front-loaded sentences with no filler: the first states what is fetched, the second routes to the sibling. Every sentence earns its place.

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?

With an output schema present and full parameter coverage, the description need not explain return values; it nonetheless enumerates them, which is slightly redundant but harmless. An agent has everything required to call it 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?

Schema description coverage is 100% and there is only one parameter, so the schema fully documents the required 'preset' identification string. The description adds no format, source, or lookup syntax beyond what the schema provides.

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?

States a specific verb (Get) and resource (grading preset) and enumerates what the preset carries (thresholds, grades, threshold configurability, certificate issuance). It clearly distinguishes itself from the plural list sibling by name.

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?

Explicitly routes the agent to edubase_get_quiz_grading_presets when the goal is to list rather than fetch one. No when-not or prerequisite guidance beyond that, but the single-alternative routing is 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

Other Tools