Skip to main content
Glama

HiveLearn

by io.github.williamechevarria
OverviewDiscussionsAdmin

hivelearn_update_quiz_question

Edit a question. Sending question_type or any answer field (options, correct_answer, accepted_answers, pairs, items) rebuilds the answer key, so supply the full answer for the effective type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
itemsNoordering only; correct order is position 1..n, or array order if positions are omitted
pairsNomatching only; at least 2 pairs
pointsNo
optionsNomultiple_choice (exactly one is_correct:true) or multi_select (one or more). 2-12 entries.
sort_orderNo
explanationNo
question_textNo
question_typeNo
correct_answerNotrue_false only
accepted_answersNofill_in_blank only; matched case-insensitively

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / accepted_answers
      Added value: +{
+  "description": "fill_in_blank only; matched case-insensitively",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / correct_answer / description
      Added value: +"true_false only"
    • addedInput schema / properties / items
      Added value: +{
+  "description": "ordering only; correct order is position 1..n, or array order if positions are omitted",
+  "items": {
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "position": {
+        "maximum": 9007199254740991,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "text": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / options / description
      Added value: +"multiple_choice (exactly one is_correct:true) or multi_select (one or more). 2-12 entries."
    • removedInput schema / properties / options / items / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / options / items / properties
      Added value: +{
+  "id": {
+    "type": "string"
+  },
+  "is_correct": {
+    "type": "boolean"
+  },
+  "text": {
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • removedInput schema / properties / options / items / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / options / items / required
      Added value: +[
+  "text"
+]
    • addedInput schema / properties / pairs
      Added value: +{
+  "description": "matching only; at least 2 pairs",
+  "items": {
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "left": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "right": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "left",
+      "right"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / question_type / enum
      Previous value: -[
-  "multiple_choice",
-  "true_false"
-]New value: +[
+  "multiple_choice",
+  "true_false",
+  "fill_in_blank",
+  "multi_select",
+  "matching",
+  "ordering"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden, and it does so meaningfully: it reveals the non-obvious destructive side effect that sending question_type or answer fields rebuilds the answer key, and it tells the agent to supply the full answer. It does not discuss permissions or reversibility, but the central mutation risk is clearly exposed.

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 efficient sentences with no filler, and the most important operational warning is placed first. Every part earns its place.

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?

For an 11-parameter mutation tool with no annotations and no output schema, the description covers the central pitfall well. However, it leaves some ambiguity about whether non-answer fields can be updated independently and what the response looks like, so it is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 45%, but the description compensates by naming the exact answer fields (options, correct_answer, accepted_answers, pairs, items) and establishing a cross-field requirement not present in the schema: changing question_type or any answer field requires the full answer set for the effective type. This adds real semantic value beyond the parameter names and property descriptions.

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 states a clear verb and resource: 'Edit a question.' The answer-key warning makes it clear this targets quiz questions, and the purpose is not a tautology of the tool name. However, it does not explicitly differentiate from siblings such as update_question_bank_item or create_quiz_question.

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 implies usage: use this to edit an existing quiz question, especially when answer-type fields are involved. It does not name alternatives or explicitly say when not to use it, but the warning about rebuilding the answer key gives practical invocation guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HiveLearn toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources