Skip to main content
Glama
Sign In
Bunpro MCP

Bunpro MCP

by Alexxanddr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_quiz_questions

Read-onlyIdempotent

Fetch the current read-only Bunpro quiz queue to inspect pending questions and plan study sessions without submitting answers or altering account data.

Instructions

Get the current read-only Bunpro quiz queue

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": "get_quiz_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so repeating 'read-only' adds little. 'Current' does imply a live, transient snapshot rather than a cached or historical result, which is a small but genuine addition; nothing is said about queue contents, ordering, or what happens when the queue is empty.

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?

A single short sentence with the resource and its read-only nature front-loaded and no filler. It is appropriately sized for a zero-parameter getter.

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?

With no output schema and no parameters, the description carries the burden of explaining what comes back, and it does not: the shape of a 'quiz queue' entry is left undefined. Given the crowded set of similarly named getters, it also omits any routing hint, leaving meaningful gaps for a tool this simple.

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 tool takes zero parameters and the schema is trivially complete, so per the baseline this is a 4. There are no parameters whose semantics the description could or should clarify.

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 ('Get the current ... quiz queue') and scopes it with 'Bunpro' and 'read-only'. It is clear what the tool returns, but it never distinguishes itself from the sibling get_queue or get_due, which an agent could easily confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no prerequisites, and no named alternative. With siblings like get_queue, get_due, and get_weak_items in the list, the agent has no textual basis for choosing this tool over them.

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