Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_question

Read-onlyIdempotent

Check if a question exists by its external ID. To get full details, use the export function.

Instructions

Check existing question. Questions are the lowest level in the EduBase hierarchy, serving as the building blocks for Quiz sets. To get question details, use the question export function!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesexternal unique question identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
activeYes
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedOutput schema / properties / active / description
      Removed value: -"question is active"
    • removedOutput schema / properties / id / description
      Removed value: -"external unique question identifier (if set for the question)"
    • removedOutput schema / properties / question / description
      Removed value: -"question identification string"
  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": {
+    "active": {
+      "description": "question is active",
+      "type": "boolean"
+    },
+    "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",
+    "active"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds context about the hierarchy but does not disclose behavioral details like what happens when the question doesn't exist or what the response contains. It does not contradict annotations, but adds minimal extra behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with two sentences that front-load the purpose and provide a pointer to an alternative. The hierarchy context is useful but could be considered extraneous; still, it is efficiently written and not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the output schema exists, the description does not clarify how this tool differs from the sibling edubase_get_question_id, which is a significant gap given the similar names. It also doesn't specify the return type or behavior on missing questions. The context is partially complete but misses key distinctions.

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% for the single parameter 'id', so the schema fully documents it. The description adds no extra parameter semantics, which is acceptable given full coverage. It meets the baseline for a well-documented schema.

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 clearly states the tool checks for the existence of a question ('Check existing question'), which is a specific verb+resource. It also gives context about the hierarchy, distinguishing it from higher-level resources. However, it doesn't explicitly differentiate from the sibling edubase_get_question_id, which might also retrieve a question, so it's not fully distinctive.

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 provides some usage guidance by pointing to the question export function for details, suggesting this tool is not for full retrieval. However, it does not mention the sibling edubase_get_question_id or explicitly state when to use this check tool versus other getters. The guidance is partial and leaves room for confusion.

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