Skip to main content
Glama
Sign In

WaterExamMath

by com.waterexammath
OverviewDiscussionsAdmin

Save study settings

save_study_settings
DestructiveIdempotent

Save the learner's grade and, optionally, their exam date and daily problem target for that grade, so later calls default to that grade and get_study_plan uses that date. Side effects: creates the learner's account on first use and REPLACES the saved grade (and the saved exam date or daily target for that grade, when given) with these values. Practice history is not touched. Safe to retry: the same values give the same result.

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>"
    },
    "name": "save_study_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
examYesExam (grade) id to save, e.g. "ca-d2"; get_exam_overview lists the ids
examDateNoExam date as YYYY-MM-DD, if the user gives one
timeZoneNoThe user's IANA time zone, e.g. "America/Los_Angeles", if known; sets which day counts as today in the plan
dailyQuestionsNoProblems per day for the study plan, if the user gives one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that a learner account is created on first use and that existing values are REPLACED, scoped per grade, while practice history is untouched. The retry semantics ('same values give the same result') reinforce the idempotentHint with concrete meaning. This is exactly the kind of destruction and side-effect detail a mutation tool needs.

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 compact sentences front-load the core action, then a third covers side effects and retry safety. Every clause carries information (defaults, account creation, replacement scope, untouched history) with no filler.

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 mutation tool with no output schema, the definition covers the write scope, side effects, data preserved, and retry behavior. An agent has everything needed to decide to call it and to predict the state change.

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 the schema already documents all four parameters including formats and examples. The description adds only the optionality framing and per-grade scoping, and it does not mention timeZone or its effect at all. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description opens with a specific verb and resource: save the learner's grade, optionally with exam date and daily problem target. It also names the downstream consumer (get_study_plan) so the agent understands the effect of the write. It does not explicitly contrast with save-like siblings such as save_mock_answers or reset_progress, so it stops short of full sibling differentiation.

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?

Usage context is clear: call it to persist a grade so later calls default to it, and pass exam date or daily target only 'if the user gives one.' There is no explicit when-not guidance or direct naming of an alternative tool for overlapping needs, so it falls short of a 5.

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