get-quiz-results
Retrieve quiz results for a course. View scores and feedback from completed quizzes.
Instructions
Bekijk de resultaten van gemaakte quizzen
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| courseId | Yes | Het ID van het vak |
Retrieve quiz results for a course. View scores and feedback from completed quizzes.
Bekijk de resultaten van gemaakte quizzen
| Name | Required | Description | Default |
|---|---|---|---|
| courseId | Yes | Het ID van het vak |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits such as permissions required, data freshness, or side effects. For a simple read operation, more transparency on expected output would be beneficial.
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?
The description is a single, front-loaded sentence with no extraneous text. It could include more detail without sacrificing conciseness.
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?
Without an output schema, the description does not explain what the results contain (e.g., scores, answers). For a tool with one parameter, this is a significant gap.
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 description coverage is 100% (one parameter fully described). According to guidelines, baseline is 3. Description adds no additional meaning beyond 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 clearly states the tool's purpose as viewing quiz results, using a specific verb-resource combination. Among sibling tools, no other tool is specifically for quiz results, so it is uniquely identifiable.
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?
No explicit guidance on when to use this tool versus alternatives. However, the context of sibling tools suggests it is the go-to for quiz results, but lack of when-not guidance keeps it at a 3.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mehdi6132/canvas-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server