Skip to main content
Glama

bind_quiz_question_banks

Attach question banks to a quiz so it draws items from them, setting order, randomization, and question limits per bank. Re-binding updates only provided fields, preserving existing settings.

Instructions

Attach question banks to a quiz, so it draws its items from them.

    Pass `quiz_id` and `question_banks`, a list of items each needing
    `question_bank_id`. Optional per item: `order` (omit and the bank is
    appended after the current last), `randomize_questions`, and
    `limit_question_count` (0 = use every question in the bank).

    RE-BINDING AN ALREADY-ATTACHED BANK IS A PARTIAL UPDATE, NOT A RESET. Only the
    fields you supply are written; anything you omit KEEPS ITS CURRENT VALUE, and an
    omitted `order` is NOT recalculated. So binding a bank that is already attached,
    with no other fields, changes nothing at all - it will not move the bank to the
    end and will not clear its settings.

    Within one call the FIRST occurrence of a bank wins; a later duplicate is
    reported as `duplicate_in_batch`. An unknown `quiz_id` fails the whole call; an
    unknown bank fails only its own row.

    Requires the `quizzes:write` OAuth scope.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quiz_idYes
question_banksYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
noteYes
totalYes
failedYes
succeededYes
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing non-obvious behavior: re-binding is a partial update, omitted fields keep current values, the first duplicate wins, unknown quiz_id fails the whole call, and unknown banks fail only their row. It also states the required OAuth scope.

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 longer than average but every sentence carries meaningful information. The key action is front-loaded, parameter details are compactly bundled, and the critical partial-update caveat is highlighted and elaborated.

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?

The description is fully self-sufficient for an agent to invoke the tool correctly: it covers what the call does, parameter semantics, edge-case behavior, error handling, and authorization. The output schema exists so return-value detail is not required in the description.

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

Parameters5/5

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

Despite 0% schema description coverage, the description thoroughly explains both parameters: quiz_id, the question_banks list, and each item's fields including order, randomize_questions, and limit_question_count. It even defines the special 0 value for limit_question_count.

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 opens with a specific verb and resource—'Attach question banks to a quiz'—and states the resulting behavior: the quiz draws its items from them. This clearly differentiates it from unbinding, listing assignments, and other quiz-related operations.

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?

It provides clear context for when to call this tool: to attach banks to a quiz, with optional ordering and question-limiting controls. It does not explicitly name alternatives or exclusion conditions, but the described semantics make the intended use evident.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server