SATCoach: AI SAT Tutor

Child's plan for this week

get_weekly_plan

Read-onlyIdempotent

This week's plan as SATCoach has it: the daily goal (questions a day), the focus skills, the test date, and the weeks left until it. For when the parent asks what the child should do this week, or wants the plan on the family calendar; it doesn't add anything to a calendar. Not for changing the plan, the daily goal, or the test date: it only reads what SATCoach already has and never makes a new plan. The parent can change the daily goal at parentUrl. Requires a connected SATCoach parent account.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description	Default
`child`	No	The child's reference, from the list of the parent's children. Optional when the parent has one child on SATCoach.

Output Schema

Name	Required	Description	Default
`asOf`	Yes
`child`	Yes
`label`	Yes
`source`	Yes
`summary`	Yes
`planDate`	Yes
`testDate`	Yes
`dailyGoal`	Yes
`parentUrl`	Yes
`weeksLeft`	Yes
`focusSkills`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the auth prerequisite (connected SATCoach parent account), that it never creates a new plan, and that it does not itself write to a calendar. The calendar point is slightly ambiguous given it is also listed as a use case, but the read-side-only behavior is clearly stated.

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 what is returned, then when to use it, then what it is not. It is a dense single paragraph with mild repetition around the calendar framing, but little is wasted.

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?

An output schema covers return values, and the description supplies the remaining essentials: account prerequisite, read-only scope, the inapplicable operations, and where to change the plan. An agent has everything needed to call it correctly or route elsewhere.

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 the schema already explains that the child reference is optional for single-child parents. The description adds no format or fallback detail beyond that, so baseline 3 applies.

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 resource and enumerates its contents (daily goal, focus skills, test date, weeks left), which makes it clearly distinct from siblings like get_focus_areas and get_progress that return narrower slices.

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?

Gives both the triggering situation (parent asks what the child should do this week, or wants the plan on the family calendar) and explicit exclusions (not for changing the plan, daily goal, or test date), plus routes the mutation case to parentUrl.

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

All SATCoach: AI SAT Tutor 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?