Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_exam_results_raw

Read-onlyIdempotent

Get raw exam results containing every user answer for detailed analysis. Use when granular response data is needed instead of display-ready summaries; extra permissions may be required.

Instructions

Get raw results for a specific exam. Only use this if very detailed results are needed! This endpoint returns raw results, including all answers given by the user. It is not meant to be displayed to the user. This might require additional permissions!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYes
usersYes
questionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedOutput schema / properties / exam / description
      Removed value: -"exam identification string"
    • removedOutput schema / properties / questions / description
      Removed value: -"most important details about the questions asked"
    • removedOutput schema / properties / users / description
      Removed value: -"details of the user and their results"
  2. Changed2 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "exam": {
+      "description": "exam identification string",
+      "type": "string"
+    },
+    "questions": {
+      "additionalProperties": {},
+      "description": "most important details about the questions asked",
+      "properties": {},
+      "type": "object"
+    },
+    "users": {
+      "description": "details of the user and their results",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "required": [
+    "exam",
+    "users",
+    "questions"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds useful behavioral context: it returns all user answers, is not meant for display, and may require extra permissions. This goes beyond the schema without contradicting the annotations.

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 compact and front-loaded with the core purpose, followed by the most important usage caveats. Every sentence adds actionable information without unnecessary verbosity.

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 single-parameter read-only tool with an output schema, the description covers the decision-relevant facts: rawness of the data, inclusion of all answers, non-display intent, and permission requirements. Nothing essential is missing for an agent to decide whether to call this tool.

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 has full description coverage for the single 'exam' parameter, so the parameter meaning is already available. The description reinforces that the tool targets a specific exam but adds no new parameter-level detail beyond the schema.

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 clearly identifies the operation as getting raw results for a specific exam, and adds the key distinguishing detail that it returns all answers given by the user. This separates it from related result-returning sibling tools like edubase_get_exam_results_user.

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 provides explicit usage context: use only when very detailed results are needed, do not display the output to users, and be aware that additional permissions may be required. It stops short of naming an alternative result endpoint, but the guidance is clear enough.

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