Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_questions

Read-onlyIdempotent

List owned quiz questions to retrieve their IDs and external identifiers, enabling content export via the export endpoint.

Instructions

List owned and managed Quiz questions. Returns the question identification strings and external identifiers. Use edubase_post_question_export to read the content of a question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage number (default: 1), not used in search mode!
limitNolimit number of results (default: 16)
searchNosearch string to filter results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • removedOutput schema / properties / questions / items / properties / id / description
      Removed value: -"external unique question identifier (if set for the question)"
    • removedOutput schema / properties / questions / items / properties / question / description
      Removed value: -"question identification string"
  2. Changed9 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / required
      Removed value: -[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "questions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "external unique question identifier (if set for the question)"
+          },
+          "question": {
+            "description": "question identification string",
+            "type": "string"
+          }
+        },
+        "required": [
+          "question"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "questions"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the important behavioral fact that this tool returns only identifiers, not full question content, and that content access is delegated to a different operation. It does not describe search or pagination quirks, but the core behavior relevant to an agent is well conveyed.

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 tightly written sentences with no filler. The primary capability is front-loaded, the return payload is stated immediately, and the sibling-tool pointer is a single clean sentence. Every part earns its place.

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 list operation with 3 optional parameters, a rich annotation set, an output schema present, and a clear description of what is returned, nothing essential is missing. An agent can select this tool and invoke it correctly with the information provided.

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%: page, limit, and search each already have descriptive text. The tool description adds no parameter-level meaning beyond what the schema provides. This matches the baseline expectation that structured schema fields carry the parameter semantics, so no extra credit or penalty is warranted.

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 opens with a specific verb and resource: 'List owned and managed Quiz questions.' It also clarifies the output scope by stating it returns only question identification strings and external identifiers, and it distinguishes itself from edubase_post_question_export. This is more than a restatement of the tool name; it tells an agent exactly what operation this tool performs.

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

Usage Guidelines5/5

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

'Use edubase_post_question_export to read the content of a question' explicitly names an alternative and the condition under which it should be used. Combined with 'Returns the question identification strings and external identifiers,' it gives the agent clear when-to-use and when-not-to-use guidance. This is the kind of direct routing that helps an agent choose correctly among many similar question-related siblings.

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