Skip to main content
Glama
Sign In
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_quiz_grading_preset

Create a new custom grading preset. Needs the custom grading feature to be enabled.

Instructions

Create a new custom grading preset. Needs the custom grading feature to be enabled.

Input Schema

NameRequiredDescriptionDefault
typeYestype of the grading preset (custom: freely named grades, at least 2 items - go-nogo-custom: successful/unsuccessful grading with a custom threshold, exactly 2 items - hungarian-school: Hungarian primary and secondary school grading (1-5), exactly 5 items - hungarian-university: Hungarian university grading (1-5), exactly 5 items)
titleYestitle of the grading preset
gradesYesthresholds and grades of the preset, in ascending order
languageNolanguage of the grading preset (default: content language of the API application owner)
successful_allNoevery grade means success, even the lowest one, only used with the custom type where the grades are labels rather than pass or fail levels (default: false)

Output Schema

NameRequiredDescriptionDefault
presetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.6
    • addedInput schema / properties / successful_all
      Added value: +{
+  "description": "every grade means success, even the lowest one, only used with the custom type where the grades are labels rather than pass or fail levels (default: false)",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv2.0.0
    • removedOutput schema / properties / preset / description
      Removed value: -"grading preset identification string"
  3. Addedv1.2.15

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the feature-flag prerequisite, which is genuinely useful deployment context, but says nothing about side effects or how existing presets interact with a new one.

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, action first and prerequisite second, with zero filler. Nothing is repeated from the schema or annotations.

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 the five parameters. With annotations covering safety and the description adding the enabling prerequisite, the definition is nearly complete; only explicit sibling routing is missing.

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 the schema itself documents type semantics, grade/threshold rules, and the ascending-order requirement in detail. The description only echoes "custom" and adds no meaning beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb (Create) and resource (grading preset), which cleanly distinguishes it from the get/patch/delete grading-preset siblings. The qualifier "custom" is slightly misleading since the schema's type enum also supports go-nogo-custom and two Hungarian schemes, but the core purpose is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description supplies one real precondition ("Needs the custom grading feature to be enabled") but never states when to choose this creation tool versus patch_quiz_grading_preset or the get variants. Usage is therefore implied by the verb rather than explicitly guided.

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