Skip to main content
Glama

edubase_get_exam_settings

Read-onlyIdempotent

Retrieve an exam's settings. For surveys, grading and results viewing settings are not returned.

Instructions

Get the settings of an exam. Surveys are never graded and their results cannot be viewed later, so the grading and the results viewing settings are not returned for them. The columns of the results export cannot be configured for surveys either, only the format and the ordering of the exported file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string
archiveYesthe users who already have a result can be archived
gradingNograding of the exam, the code of the grading preset in use, "custom" for a manually configured grading, or "none" when grading is disabled, null if the setting of the Quiz set is used (never returned for surveys)
pausableYestests can be paused and continued later during the exam period
roundtimeYestime limit of a single question in seconds (as a number), turn based Quiz sets only, null if the setting of the Quiz set is used, or 0 if there is no time limit
timelimitYestime limit of the whole test in seconds (as a number), null if the setting of the Quiz set is used, or 0 if there is no time limit
hide_gradeNothe grade is hidden on the results page
export_sortYesordering of the examinees in the exported results file (default: the same order they are listed in on the users page of the exam, name: by the name of the examinees)
hide_pointsNothe points are hidden during the test and on the results page
nonblockingYesexam accounts are exclusively assigned to the exam and cannot be assigned to other exams during the exam period
results_urlNoURL where examinees can look up their own results with the identifier (only present if the identifier based results page is available)
export_statsNothe statistics of every question are exported (never returned for surveys)
freeze_roundYesthe current round of the exam is frozen, no new round can be started
results_pageNothe examinees are redirected to the results page after the test
view_resultsNowhen the examinees can see their results (after: right after the test is submitted, until the end of the exam, always: any time during the exam period, the examinees can log back in to see their results, datetime: after the test is submitted, and again from the start of the results viewing period, datetime_blind: only in the results viewing period, the solutions and the details of the evaluation are hidden right after the test, manual: only after the result is published separately, test by test, none: never), never returned for surveys
export_formatYesformat of the exported results file (csv: semicolon separated values, xlsx: Excel 2007+ workbook)
export_genderNothe gender of the registered examinees is exported (never returned for surveys)
export_pointsNothe points scored on every question are exported (never returned for surveys)
export_skillsNothe skill results of the examinees are exported, only exported when the Quiz set of the exam has skills (never returned for surveys)
export_answersNothe answers given by the examinees are exported (never returned for surveys)
export_suspicionNothe suspicious test taking indicator is exported (never returned for surveys)
show_in_lasthourNothe results are only shown in the last hour of the exam
export_attendanceNothe attendance of the examinees is exported, read only as the attendance is configured together with its source on the interface (never returned for surveys)
grading_thresholdNothreshold of the grading in percentage (only present if a threshold is configured for the exam)
view_results_startNostart of the results viewing period (only present if view_results is datetime or datetime_blind)
hide_ingame_resultsNothe results are hidden while the test is taken
export_custom_fieldsNothe user data fields filled in by the examinees are exported (see edubase_get_exam_fields), never returned for surveys
export_finished_onlyNoonly the examinees who finished their test are exported (never returned for surveys)
view_results_identifierNolabel of the custom user data field the examinees can look up their results with (only present if view_results is datetime or datetime_blind)
Install Server

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, so the safety profile is clear. The description adds valuable context about survey behavior—that grading and results-viewing settings are not returned for surveys, and export columns are not configurable—which enriches the agent's understanding beyond structured metadata. No contradiction exists.

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 two sentences with zero waste. The core purpose is front-loaded, and the additional detail about surveys is relevant and succinct. No irrelevant information is included.

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?

For a simple GET with one parameter and read-only annotations, the description is complete. It covers the main use case and flags the special case of surveys with enough detail for an agent to call the tool correctly and understand the output expectations. The output schema further eliminates the need to describe return structures.

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?

The input schema covers the single 'exam' parameter with a description ('exam identification string'), at 100% coverage. The description does not add further detail about parameter format or usage, but with full schema coverage the baseline of 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 verb 'Get' with resource 'settings of an exam' states exactly what the tool does. It also clarifies that for surveys, grading and results-viewing settings are omitted, and export columns are not configurable, which further defines the scope of the returned data. This clearly distinguishes it from sibling tools like POST/PUT/PATCH exam settings.

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 implies this is for retrieving exam settings based on the GET verb, but it does not explicitly state when to use it versus the sibling tools for creating or updating settings. The survey-specific details provide some context about which settings are relevant, but no exclusions or alternative recommendations are mentioned.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EduBase/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server