Skip to main content
Glama

Check a practice answer

check_answer
Read-onlyIdempotent

Score the person's choice for a CRLN practice decision. Returns the score out of 4, the feedback, the rule it rests on and a link to continue that scenario in CRLN. It never says which option is best. Call it only after the person has chosen.

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": {
      "scenario_id": "<scenario_id>",
      "choice": "<choice>"
    },
    "name": "check_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
choiceYesThe letter the person chose, for example B.
attempt_idNoThe attempt_id from practice_decision.
scenario_idYesThe scenario_id from practice_decision.

Output Schema

NameRequiredDescriptionDefault
linkNoA link straight to the page on CRLN.
ruleNo
scoreNo
choiceNo
optionNo
out_ofNo
resultNo
feedbackNo
attempt_idNo
consequenceNo
scenario_idNo
first_answer_standsNo
decisions_in_scenarioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is low. The description still adds real behavioral value: the score is out of 4, feedback and the underlying rule are returned, and it explicitly "never says which option is best" – an important expectation to set for the caller.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and then the return contents and the precondition. "in CRLN" appears twice, a small redundancy, but nothing is padded.

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?

The output schema already defines return values, yet the description usefully characterizes them, and it supplies the ordering constraint. Only edge behavior – invalid letters, retries with attempt_id – is left unstated, which is minor for a read-only scoring call.

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 100%, so choice, scenario_id and attempt_id are already documented, including their provenance from practice_decision. The description adds no syntax or format detail beyond what the schema states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb plus resource: "Score the person's choice for a CRLN practice decision." It clearly reads as an evaluation tool rather than a scenario or rule-explanation tool, but it never names a sibling to contrast with, so differentiation is inferred rather than stated.

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?

Gives an explicit precondition: "Call it only after the person has chosen." That anchors the sequencing after practice_decision. It does not, however, point to explain_rule for deeper rationale or say what to do if the person hasn't chosen yet.

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