Skip to main content
Glama

list_question_banks

Read-onlyIdempotent

Locate reusable question banks in your organization by exact name or recent changes. Returns paginated results; check has_more and use cursor to fetch additional pages.

Instructions

Find reusable question banks in this organization, by name or last change.

    A question bank is a pool of exam items shared across quizzes, so the same
    certification questions can back several assessments without being duplicated.

    Returns ONE PAGE. Check `has_more` and call again with `next_cursor` before
    telling the user how many banks exist or that one is absent. `filter_name` is an
    EXACT match, case-insensitive.

    Does not return the banks' questions - use `list_questions` with
    `filter_question_bank_id`. Requires the `question-banks:read` OAuth scope.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNo
filter_nameNo
page_cursorNo
filter_updated_sinceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
has_moreYes
next_cursorNo
question_banksYes
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds valuable behavioral context: pagination behavior, exact case-insensitive match for filter_name, and that it does not include questions. It also notes the OAuth scope, going beyond annotations without contradiction.

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 concise and well-structured, with the main purpose front-loaded, followed by pagination caveats, related tool routing, and scope requirement. Each sentence adds value, and there is negligible redundancy.

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?

For a listing tool with an output schema, this description covers all essential aspects: purpose, page-limited behavior, pagination usage, filter matching rules, exclusion of questions, and required OAuth scope. Nothing critical is missing for an agent to call it correctly.

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 0%, so the description must compensate. It does explain filter_name semantics (exact match, case-insensitive) and implies page_cursor via pagination instructions, but page_size and filter_updated_since are not detailed beyond the schema. This partial compensation justifies a middle score.

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 clearly states the tool finds question banks by name or last change, defines what a question bank is, and differentiates from sibling tools like list_questions and get_question_bank. It explicitly notes it does not return questions, leaving no ambiguity.

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?

Provides explicit usage guidance: it returns only one page, instructs checking has_more and using next_cursor before concluding about counts, and directs users to list_questions for the banks' questions. Also specifies the required OAuth scope, which is critical for invocation.

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