Skip to main content
Glama

Grade quiz answers

grade_answers
Read-onlyIdempotent

Grade a quiz created by practice_quiz. Returns which answers were right, the correct option, and a one-line explanation per question. This is practice feedback, not an exam score.

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": {
      "quiz_id": "<quiz_id>",
      "answers": "<answers>"
    },
    "name": "grade_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYes
quiz_idYesThe quiz_id returned by practice_quiz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond them by disclosing the response shape (per-question correctness, correct option, explanation) and framing the result as formative feedback rather than an official score. It doesn't state behavior on invalid quiz_id or mismatched answer counts, which is the only remaining gap.

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?

Three short sentences, front-loaded with the action and the producing sibling, then the return contents, then the important framing caveat. Nothing is redundant or buried.

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?

With no output schema, the description does the necessary work of explaining what comes back per question, and the tool's complexity is low. A note on failure modes (unknown quiz_id, extra or duplicate qids beyond maxItems 10) would make it complete, but nothing essential for a correct call is missing.

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 description coverage is 50%: quiz_id and the qid/choice leaves are documented, but the answers array and its item object carry no descriptions, and the maxItems=10 constraint is undocumented anywhere. The description adds no parameter-level meaning beyond the schema, so this lands at the baseline for partial coverage rather than higher.

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?

States a specific verb and resource ('Grade a quiz created by practice_quiz') and explicitly ties the input to the sibling that produces it. The return contents are enumerated (right/wrong, correct option, one-line explanation), so an agent can distinguish this from retrieval tools like lookup_word or practice_quiz.

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?

Establishes the usage context clearly: this follows practice_quiz and produces practice feedback rather than an exam score, which sets expectations about authoritative grading. It stops short of explicit exclusions (e.g., don't use for exam scoring or for quizzes not created by practice_quiz), so it's clear context without stated when-not-to-use rules.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources