Skip to main content
Glama

Check an answer and explain every option

check_answer

Grades the user's choice and returns an explanation for EVERY option, including the ones they did not pick. On this exam two options are frequently defensible and only one is credited, so the reasons the wrong options lose are the part worth teaching.

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": {
      "exam": "<exam>",
      "question_id": "<question_id>",
      "selected": "<selected>"
    },
    "name": "check_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
examYesExam slug.
selectedYesOption letters the user chose, e.g. ["B"] or ["B","D"].
question_idYesThe id from get_practice_question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / exam / enum
      Previous value: -[
      -  "ccar-p",
      -  "ccdv-f",
      -  "ccao-f",
      -  "ccar-f",
      -  "ccdv-p"
      -]New value: +[
      +  "ccar-p",
      +  "ccdv-f",
      +  "ccao-f",
      +  "ccar-f",
      +  "ccdv-p",
      +  "ccar-p-v2",
      +  "ccdv-f-v2",
      +  "ccao-f-v2"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / exam / enum
      Previous value: -[
      -  "ccar-p",
      -  "ccdv-f",
      -  "ccao-f",
      -  "ccar-f"
      -]New value: +[
      +  "ccar-p",
      +  "ccdv-f",
      +  "ccao-f",
      +  "ccar-f",
      +  "ccdv-p"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no output schema, the description usefully discloses the shape of the response (an explanation for every option, not just the chosen one), which is real added value. However, annotations declare readOnlyHint=false while the description reads as a pure grading/read action; it never says the submission is recorded or feeds progress (relevant given the my_progress sibling), which is a meaningful omission for a non-read-only tool.

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?

Two sentences, front-loaded with the action and its distinguishing output scope, followed by the pedagogical rationale. No filler and no repetition of the name or title.

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

Completeness3/5

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

For a three-parameter tool with annotations but no output schema, the description covers what is returned well enough that return values needn't be enumerated. It falls short on side effects: since readOnlyHint is false, an agent cannot tell from the definition whether submitting an answer alters stored progress or is repeatable.

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 100% and all three parameters are documented in the schema, including the enum of exam slugs and the selected-letters format, so the description adds no parameter meaning of its own. Baseline 3 applies when the schema carries the full burden.

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 ('Grades the user's choice') and the exact scope of its output ('an explanation for EVERY option, including the ones they did not pick'). This clearly separates it from get_practice_question, which supplies questions rather than grading them.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the emphasis on teaching why wrong options lose signals it should be used after attempting a question. There is no explicit when-to-use/when-not statement, and no mention of prerequisites such as having fetched the question first (that hint lives only in the schema's question_id text).

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