Skip to main content
Glama

edubase_get_question

Read-onlyIdempotent

Fetch an existing question by its unique ID to inspect details and confirm it before building quiz sets.

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!

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "edubase_get_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesexternal unique question identifier

Output Schema

NameRequiredDescriptionDefault
aiYes
idNo
activeYes
questionYes
ai_reviewedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.9
    • addedOutput schema / properties / ai
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / ai_reviewed
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "question",
      -  "active"
      -]New value: +[
      +  "question",
      +  "active",
      +  "ai",
      +  "ai_reviewed"
      +]
  2. 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"
  3. 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"
      +}
  4. 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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful contextual information about the EduBase hierarchy and implicitly signals that this tool is not the detail-retrieval endpoint by pointing to the export function. It does not add permission, rate-limit, or output-shape behavior beyond the annotations and output schema.

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 short and front-loads the action ('Check existing question'). The hierarchy sentence is contextual but slightly non-essential, and the export pointer is valuable. Overall it is efficient with minimal 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?

With one fully documented parameter, an output schema, and annotations covering safety, the description provides enough context to call the tool correctly. The only weakness is the vague verb 'check', which leaves the exact return semantics slightly ambiguous despite the output schema.

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%, and the single 'id' parameter is documented as the external unique question identifier. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (question) and a vague verb phrase ('Check existing question'), but 'check' does not specify whether it retrieves, validates, or merely confirms existence. It does distinguish itself somewhat from the export function by directing detail retrieval elsewhere, but it does not differentiate clearly from siblings such as get_questions or get_question_id.

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 gives explicit guidance to use the question export function for full details, which is a named alternative and condition. It does not explain when to use this tool versus get_questions or get_question_id, but the core alternative routing is clear.

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