WaterExamMath

Save timed-set answers

save_mock_answers

Idempotent

Save some or all answers of an OPEN timed set from start_mock_exam as a draft, by problem number (1-based) and letter. Only the listed problems change; the others keep their saved answer. Any answer can be changed again until the set is submitted (send a new letter, or an empty string to leave that problem blank again), so nothing is lost by saving. Nothing is scored and nothing is recorded into the learner's progress until submit_mock_exam. Returns how many problems are answered and which numbers are still blank. Side effects: updates the unsubmitted draft on that one open timed set and nothing else. Safe to retry: the same answers give the same draft. Only submit_mock_exam makes the answers final.

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": {
      "mockExamId": "<mockExamId>",
      "answers": "<answers>"
    },
    "name": "save_mock_answers"
  }
}

Input Schema

Name	Required	Description	Default
`answers`	Yes	Problem numbers with the letter chosen, e.g. [{ number: 1, answer: "B" }, { number: 2, answer: "" }]
`mockExamId`	Yes	The id returned by start_mock_exam

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare non-readOnly, idempotent and non-destructive; the description adds real context on top: nothing is scored or recorded until submit_mock_exam, side effects are limited to one draft, and retries are safe because the same answers produce the same draft. It also discloses the return shape (answered count plus blank numbers), which the tool has no output schema for.

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?

Front-loaded with the action and precondition, then the partial-update rule, then the scoring caveat. Slightly redundant at the tail: 'Safe to retry: the same answers give the same draft' restates idempotentHint, and 'Only submit_mock_exam makes the answers final' echoes the earlier no-scoring sentence.

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

Completeness5/5

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

For a two-parameter mutation tool with no output schema, everything an agent needs is present: precondition (open set), partial-update semantics, clearing behavior, reversibility, idempotency, scope of side effects, and the returned counts — no gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the answers array is already documented with an example, so the schema carries most of the load. The description still adds meaning beyond it: numbering is 1-based, entries are keyed by problem number and letter, and an empty string deliberately blanks a problem — none of which the schema states.

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 ('Save some or all answers of an OPEN timed set from start_mock_exam as a draft') and names the sibling it complements, so an agent can distinguish it from submit_mock_exam and start_mock_exam without opening a schema.

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

Usage Guidelines5/5

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

Explicitly scopes use to an OPEN timed set, states the update is partial ('Only the listed problems change'), explains how to clear an answer, and names submit_mock_exam as the point where answers become final. When-not guidance is implied through the open-set precondition and the submit alternative.

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

All WaterExamMath tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?