Skip to main content
Glama

edubase_get_questions

Read-onlyIdempotent

Lists owned and managed quiz questions with identification strings, external identifiers, and AI-generated markings, helping you locate items before exporting and reading their content.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
questionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.9
    • addedOutput schema / properties / questions / items / properties / ai
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / questions / items / properties / ai_reviewed
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / properties / questions / items / required
      Previous value: -[
      -  "question"
      -]New value: +[
      +  "question",
      +  "ai",
      +  "ai_reviewed"
      +]
  2. 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"
  3. 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"
      +}
  4. First observedv1.0.22

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description usefully adds what the response contains, but says nothing about pagination behavior beyond what the schema notes, result caps, or the 'not used in search mode' nuance for page.

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 core purpose, followed by the return summary and the routing hint. Nothing is redundant or padded.

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 a full parameter schema, an output schema, and complete annotations, the description covers the essentials and adds a sibling routing hint. The only gap is that the distinction from get_question / get_quiz_questions is implied rather than stated.

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%, so page, limit and search are fully documented in the schema itself. The description adds no extra semantics for these parameters, so the baseline 3 applies.

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?

States a specific verb and resource ('List owned and managed Quiz questions') and even enumerates the returned fields (identification strings, external identifiers, AI markings). It does not, however, distinguish itself from close siblings like get_question or get_quiz_questions, so an agent must infer whether this lists a library of questions vs. questions in one quiz.

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?

Explicitly names the alternative and its condition: 'Use edubase_post_question_export to read the content of a question.' That gives a clean read-list vs. read-content split, but no guidance on when to prefer get_question or get_quiz_questions.

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