Skip to main content
Glama

delete_quiz

Delete a quiz from the LMS by specifying its unique slug identifier.

Instructions

Delete a quiz.

Args: quiz: The quiz name (slug).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations exist, so the description carries the full burden. It only states 'Delete a quiz' without disclosing whether the deletion is permanent, what side effects occur (e.g., removing questions, embedding), or any required permissions. This is insufficient for a destructive operation.

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 extremely concise with two sentences, the first stating the purpose and the second defining the parameter. No redundancy or unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's destructive nature and the presence of an output schema, the description lacks important context such as irreversibility, effects on related data (e.g., quiz questions, lesson embeddings), and return value. An output schema exists but is not referenced, reducing completeness.

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 coverage is 0%, and the description adds a single line: 'quiz: The quiz name (slug).' While this clarifies the parameter as a slug, it does not explain how to obtain the slug or any constraints. Adequate but minimal value added.

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 'Delete a quiz,' which is a specific verb and resource. It clearly distinguishes from sibling tools like delete_chapter or delete_lesson, as it is the only delete tool for quizzes.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use delete_quiz versus simply unenrolling or archiving. There is no mention of prerequisites or situations to avoid deletion.

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

Install Server

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/anggun-indra/frape-lms-mcp-tools'

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