Skip to main content
Glama
Sign In

WaterExamMath

by com.waterexammath
OverviewDiscussionsAdmin

Start a timed mock exam

start_mock_exam

Start a timed math set for one exam (grade): problems spread over its math topics, with a time limit. Optional count (10, 25 or 50 problems, default 25) and minutes (15, 30, 60, 90 or 120, default 60). It covers the math portion only. Returns the set id, the deadline and every problem WITHOUT answers; submit_mock_exam scores all answers at once. Side effects: creates the learner's account on first use, a timed set record and a usage record. If a set is already open for that grade (even past its deadline) that set is returned instead and nothing new is created; after it is submitted, calling again starts a new one. Nothing is closed or cancelled by this call. A set left open more than 7 days past its deadline is closed without a score by a daily cleanup. Timed sets are not limited per month; at most 12 new timed sets can be started per hour per account (over it, nothing is created and the call can be retried later).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_mock_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
examNoExam (grade) id, e.g. "ca-d2" or "ca-t1". Leave out to use the grade the user saved (save_study_settings); get_exam_overview lists the ids.
countNoNumber of problems: 10, 25 or 50 (default 25)
minutesNoTime limit in minutes: 15, 30, 60, 90 or 120 (default 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses account creation on first use, that an open set (even past deadline) is returned instead of creating a new one, that nothing is closed by this call, the 7-day cleanup abandonment rule, and the 12-per-hour rate limit with retry semantics. This explains the non-idempotent behavior precisely.

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?

Purpose and return shape are front-loaded, and side effects are grouped at the end. It's dense but nearly every clause carries information; the restated count/minutes enums are the only clearly redundant text.

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?

With no output schema, the description still explains the return payload (set id, deadline, problems without answers). For a mutating, rate-limited tool it covers creation semantics, reuse behavior, and cleanup rules thoroughly.

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%, so the enum values, defaults, and the exam examples are already documented in the schema. The description largely restates those values and adds no format or interaction guidance beyond what parameters already state.

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 ('Start a timed math set for one exam (grade)') and scopes the content ('problems spread over its math topics, with a time limit'). It clearly separates itself from submit_mock_exam ('scores all answers at once') and notes it covers the math portion only.

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 says to use submit_mock_exam to score answers, and describes what happens when a set is already open versus already submitted. The math-only restriction and the retry guidance for the hourly cap tell the agent when this tool is and isn't the right call.

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

All WaterExamMath toolsInspect
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