Skip to main content
Glama

questionBank_addItem

Adds one question/item to a question bank. Call questionBank_blockTypeColumns(riddleType) first to see the valid blockType values for this bank and which "columns" each one expects - there is no single universal shape. The item is added to the bank's draft; call questionBank_publish to make it something a QuestionBank block actually draws. Rejected for a public template id, see questionBank_templateList.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
columnsYesThe question content, as {columnName: [values]}. Which column names are expected depends on the bank's riddleType AND the blockType, so read them off questionBank_blockTypeColumns rather than guessing: an unknown column name is rejected, naming the column it did not recognise and listing the valid ones. E.g. a "Quiz" bank's "SingleChoice" takes {"QUESTION": ["Capital of France?"], "CORRECT_CHOICE": ["Paris"], "INCORRECT_CHOICE": ["London", "Berlin"]}, a "Poll" bank's "SingleChoice" {"QUESTION": [...], "CHOICE": [...]} instead, a Poll answer never being right or wrong.
categoryYesThe item's category - free text, used to filter what a QuestionBank block draws (see the "questionBankCriteria" of the QuestionBank block type).
blockTypeYesThe block type this question is shaped for, e.g. "SingleChoice"/"MultipleChoice". questionBank_blockTypeColumns lists every blockType valid for this bank's riddleType and the "columns" each expects.
difficultyYesThe item's difficulty, 1-10 - also used to filter what a QuestionBank block draws.
questionBankIdYesThe ID of the question bank to add the item to.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the single 'idempotentHint: false' annotation, the description reveals that the item is placed into a draft, is not live until published, and that validation depends on both the bank's riddleType and the chosen blockType. It also discloses a rejection edge case for public template ids, which the schema does not capture.

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 compact and front-loaded with the core action, followed only by the highest-value operational caveats: discover the shape first, remember the item starts as draft, and avoid public template ids. Every sentence carries necessary information.

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?

Given the high schema coverage and the tool's actual complexity, the description covers the required flow, the draft state, the publish step, the shape-dependency, and the public-template rejection. No output schema exists, but the single-item mutation does not demand return-value documentation here.

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?

The input schema already covers all parameters at 100% with detailed descriptions and examples, so the tool description does not need to repeat parameter-level information. It adds useful cross-parameter meaning by emphasizing that there is no single universal columns shape and directing the agent to use questionBank_blockTypeColumns as the authoritative source for valid values.

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 states a specific verb and resource: 'Adds one question/item to a question bank.' It also differentiates itself by mentioning the draft workflow and the dependency on questionBank_blockTypeColumns, which separates it from related questionBank tools like updateItem or publish.

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?

The description gives explicit usage instructions: call questionBank_blockTypeColumns(riddleType) first to discover valid blockTypes and column shapes, call questionBank_publish after adding to make the item drawable, and avoid public template ids with a pointer to questionBank_templateList. This is strong when-to and when-not-to guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Tools are largely distinct by name and detailed descriptions, with clear prefixes (riddle_builder_*, questionBank_*, stats_*). Some potential confusion exists among the stats tools (stats_fetch vs stats_overview_fetch vs breakdowns) but descriptions clarify their different scopes. Overall, an agent can usually pick the right tool.

Naming Consistency4/5

Naming follows a predictable prefix+verb pattern within each domain (e.g., riddle_builder_quiz, riddle_builder_poll; riddle_get, riddle_publish). Minor inconsistencies exist, like the camelCase 'questionBank' and 'riddleTemplate' prefixes vs snake_case elsewhere, and 'stats_overview_fetch' ordering, but these are not chaotic and remain readable.

Tool Count1/5

With 62 tools, this far exceeds the recommended 3-15 range and even the 25+ threshold. While the server covers a broad domain, the extreme number overwhelms and makes tool selection harder, fitting the 'extreme mismatch' criterion for 50+ tools.

Completeness5/5

The tool surface is exceptionally comprehensive, covering creation, reading, updating, deleting, publishing, unpublishing, moving, tagging, template management, question banks, palettes, and various stats breakdowns. There are no obvious gaps in the lifecycle of managing interactive content, and all apparent operations are supported.

Resources