Skip to main content
Glama
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii

get_quiz_review

Review a finished quiz attempt to see each question, your chosen answer, its mark, and the correct answer when the teacher allows review; returns the latest attempt by default.

Instructions

Review a finished quiz attempt (module_id from get_course_contents): every question with the chosen answer marked [x], its mark and the correct answer, when the teacher allows review. Default is the latest attempt.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course_id": "<course_id>",
      "module_id": "<module_id>"
    },
    "name": "get_quiz_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
module_idYes
attempt_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the review contents, the teacher-permission condition, and the default attempt behavior. It does not cover error cases, pagination, or authentication requirements, but the core behavior is clearly stated.

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 a single dense sentence that front-loads the action and resource, then adds output details, conditional availability, and the default attempt in a compact sequence. Every clause adds useful information without repetition.

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

Completeness4/5

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

There is no output schema or annotation coverage, so the description appropriately explains what is returned and when review is permitted. It is nearly complete for invocation, though it lacks detail on errors or behavior when no review is available.

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%, so the description must compensate. It adds meaning for module_id (source: get_course_contents) and attempt_id (default: latest attempt), but it does not explain course_id or clarify attempt_id behavior when supplied. This is partial compensation, appropriate for a 3.

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 uses a specific verb ('Review') and resource ('a finished quiz attempt') and explains what the review contains: every question, the chosen answer marked [x], its mark, and the correct answer. This makes it readily distinguishable from generic grade or course-content tools, even without naming a sibling explicitly.

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

Usage Guidelines4/5

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

It gives clear contextual guidance: the quiz attempt must be finished, review is available only 'when the teacher allows review,' and the default is the latest attempt. It also points to get_course_contents for module_id. It does not explicitly compare itself with get_grades or other siblings, so it stops short of full alternative routing.

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