Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_quiz_grading_preset

Read-onlyIdempotent

Retrieve a quiz grading preset to view its thresholds, grades, configurable threshold status, and certificate issuance options. Use this to inspect preset details before applying grading rules.

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

TableJSON Schema
NameRequiredDescriptionDefault
presetYesgrading preset identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownYes
typeYes
usedYes
titleYes
gradesYes
presetYes
languageYes
certificatesYes
configurableYes
organizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
+]
  3. Addedv1.2.15

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds what information is included rather than disclosing new behavioral traits such as failure modes or identifier requirements. No contradiction with the annotations is present.

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 tight sentences: the first states the operation and its key outputs, the second routes list requests to the correct sibling tool. There is no redundant phrasing or repetition of structured information.

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 simple one-parameter read operation with a single required preset identifier, full annotations, and an output schema. The description names the resource type, the relevant return content, and the correct sibling for listing, which is complete for an agent to select and invoke the tool 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%: the only parameter, 'preset', is documented as a grading preset identification string in the input schema. The description does not add further meaning about the parameter's format or where to obtain a valid identifier, but with full schema coverage the baseline 3 is appropriate.

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 ('Get') and a clear resource ('a grading preset') while enumerating the meaningful output dimensions: thresholds, grades, threshold configurability, and certificate issuance. It also distinguishes itself from the plural listing sibling by explicitly naming edubase_get_quiz_grading_presets for that purpose.

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 tells the agent that listing presets is handled by edubase_get_quiz_grading_presets, which clarifies the singular tool's scope. It does not explicitly discuss the create/update/delete preset siblings, but the retrieval-vs-listing distinction is clear and adequate for this read-only tool.

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