List quizzes, optionally scoped to a course or a specific lesson. Each quiz belongs to one lesson.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size, default 20 | |
| offset | No | Rows to skip, default 0 | |
| course_id | No | ||
| lesson_id | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It mentions optional scoping and the domain constraint that each quiz belongs to a lesson, adding useful context. However, it doesn't clarify whether course_id and lesson_id can be combined or what the output format looks like.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action. The second sentence adds useful domain relationship without fluff. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple, but the description doesn't specify behavior when both course_id and lesson_id are provided, and there's no output schema. It's adequate for basic list usage but has gaps around filter interaction and return value details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 50%; course_id and lesson_id lack descriptions. The description's mention of 'scoped to a course or a specific lesson' gives meaning to these otherwise undocumented parameters, while limit/offset are already described in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'List quizzes', a specific verb+resource pair. It clearly distinguishes from sibling tools like hivelearn_get_quiz (singular) and hivelearn_list_quiz_questions (different resource).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states the tool lists quizzes and can be optionally scoped to a course or lesson, giving clear context for when to use it. It does not explicitly mention alternatives, but the scoping context implies when this list tool is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct resource/action combination, and similar-looking tools are carefully differentiated in descriptions (e.g., get_course_structure vs list_course_modules, update_lesson vs update_lesson_content). There is no meaningful overlap or ambiguity between tools.
All tools use a consistent 'hivelearn_<verb>_<noun>' pattern with common verbs (get, list, create, update). The only minor deviation is 'add' vs 'create' (add_track_course vs create_track), but this is semantically appropriate and does not disrupt the overall pattern.
With 57 tools, the server is significantly over the recommended range and exceeds the 25+ threshold for 'too many'. While the broad domain (courses, community, analytics) justifies a large surface, this many tools makes selection overwhelming for agents and suggests a need for consolidation or sub-servers.
The tool surface covers create, read, and update for most core entities (courses, lessons, quizzes, tracks, posts, events, resources), plus publishing/verification and analytics. However, there are notable gaps: no delete operations for courses, lessons, modules, quizzes, posts, events, resources, or enrollments, and no way to remove a course from a track. These lifecycle holes are significant but not fatal for common workflows.
