EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_post_exam_fields

Updates an exam’s built-in examinee fields and replaces its full custom field list; clears the results identifier if a selected custom field is no longer unique free text.

Instructions

Change the built-in user data fields of an exam, and replace the complete list of its custom fields. The view_results_identifier setting of the exam is cleared when the selected custom field is not a unique free text field anymore.

Input Schema

TableJSON Schema

Name	Required	Description
`exam`	Yes	exam identification string
`name`	No	request the full name of the examinee (true: use the field with its default label, false: do not use the field but keep its other settings, any other value is used as the label of the field)
`email`	No	request the email address of the examinee (true: use the field with its default label, false: do not use the field but keep its other settings, any other value is used as the label of the field)
`phone`	No	request the phone number of the examinee (true: use the field with its default label, false: do not use the field but keep its other settings, any other value is used as the label of the field)
`fields`	No	the custom fields of the exam, in the order they are shown to the examinee, the submitted list replaces the current one so send every custom field that should be kept, use edubase_delete_exam_fields to remove every custom field

Output Schema

TableJSON Schema

Name	Required	Description	Default
`exam`	Yes
`name`	Yes
`email`	Yes
`phone`	Yes
`fields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.3Sep 30, 2026
- changedOutput schema / properties / fields / items / required
```
Previous value: -[
-  "label",
-  "type",
-  "required"
-]New value: +[
+  "label"
+]
```

Changed19 schema fields changedv2.0.0Sep 15, 2026

removedOutput schema / properties / email / description

Removed value: -"the email address of the examinee is requested (false: the field is not used, true: the field is used with its default label, otherwise the custom label of the field)"

removedOutput schema / properties / exam / description
```
Removed value: -"exam identification string"
```
removedOutput schema / properties / fields / description
```
Removed value: -"the custom fields of the exam"
```
removedOutput schema / properties / fields / items / properties / description / description
```
Removed value: -"description shown under the field (if set)"
```

removedOutput schema / properties / fields / items / properties / filtering / description

Removed value: -"short labels the examinees are grouped and filtered with in the exam manager and the reports, keyed by option (select fields only, if set)"

removedOutput schema / properties / fields / items / properties / from / description
```
Removed value: -"lowest selectable value (from-to fields only)"
```
removedOutput schema / properties / fields / items / properties / icon / description
```
Removed value: -"Font Awesome icon class name of the field (if set)"
```
removedOutput schema / properties / fields / items / properties / label / description
```
Removed value: -"label of the field, shown to the examinee"
```
removedOutput schema / properties / fields / items / properties / maxlength / description
```
Removed value: -"maximum length of the value (free text fields only, if set)"
```
removedOutput schema / properties / fields / items / properties / minlength / description
```
Removed value: -"minimum length of the value (free text fields only, if set)"
```
removedOutput schema / properties / fields / items / properties / options / description
```
Removed value: -"the selectable options (select fields only)"
```

removedOutput schema / properties / fields / items / properties / pattern / description

Removed value: -"regular expression the value has to match (free text fields only, if set)"

removedOutput schema / properties / fields / items / properties / required / description
```
Removed value: -"the field has to be filled in"
```

removedOutput schema / properties / fields / items / properties / step / description

Removed value: -"difference between the selectable values (from-to fields only, if set)"

removedOutput schema / properties / fields / items / properties / to / description
```
Removed value: -"highest selectable value (from-to fields only)"
```
removedOutput schema / properties / fields / items / properties / type / description
```
Removed value: -"type of the field"
```

removedOutput schema / properties / fields / items / properties / unique / description

Removed value: -"the value has to be unique within the exam (free text fields only, if set)"

removedOutput schema / properties / name / description

Removed value: -"the full name of the examinee is requested (false: the field is not used, true: the field is used with its default label, otherwise the custom label of the field)"

removedOutput schema / properties / phone / description

Removed value: -"the phone number of the examinee is requested (false: the field is not used, true: the field is used with its default label, otherwise the custom label of the field)"

Addedv1.2.15Sep 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds important behavioral context beyond annotations: replacing the complete custom field list and clearing view_results_identifier when the selected custom field is no longer unique. This is valuable and not in the annotations or schema. However, it doesn't cover all mutation effects (e.g., what happens to other settings).

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 sentences, front-loaded with the primary action and followed by a critical side-effect. Every sentence earns its place with no waste.

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?

Given the complexity (5 params, nested array), annotations, and an output schema, the description is fairly complete. It covers the main action and a key side-effect. It could mention response format or prerequisites, but the output schema covers returns.

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 coverage is 100%, so the schema fully documents all parameters. The description adds the behavioral note about clearing view_results_identifier, which is not in the schema, but does not add meaning to the individual parameters beyond what the schema provides. Baseline 3 is appropriate.

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?

The description states a specific dual action: change built-in user data fields and replace the complete list of custom fields. This clearly identifies the verb and resource. It does not, however, explicitly distinguish itself from edubase_post_exam_settings or other exam field tools, though the schema and name clarify.

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?

Usage is implied by the description of replacing the custom field list, and the schema mentions using edubase_delete_exam_fields to remove all custom fields. However, there is no explicit guidance on when to use this tool versus edubase_post_exam_settings or edubase_get_exam_fields. The context is inferable but not stated.

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

Deploy Server