SATCoach: AI SAT Tutor

Child's recent tutor updates

get_tutor_updates

Read-onlyIdempotent

The tutor's most recent updates sent to the parent about the child, newest first, up to limit (at most 5), each with its date, type, and text. These are the updates the parent portal shows: only ones actually sent to the parent. With none sent yet, the list is empty. For when the parent asks what the tutor said lately. Not for getting the tutor's private notes, drafts, or unsent updates: those are never returned. 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",
      "limit": 3
    },
    "name": "get_tutor_updates"
  }
}

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.
`limit`	No	How many of the most recent updates to return, at most 5.

Output Schema

Name	Required	Description	Default
`asOf`	Yes
`child`	Yes
`label`	Yes
`source`	Yes
`summary`	Yes
`updates`	Yes
`parentUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, which already mark this as read-only, idempotent, and non-destructive, the description discloses that only updates actually sent to the parent are returned, that ordering is newest first, that the result can be empty, and that access requires a connected parent account. Those are meaningful behavioral constraints an agent could not infer from the annotations alone.

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?

The description is front-loaded and packs the core purpose, ordering, limit, and returned fields into the first sentence. It repeats the sent-only filtering constraint more than once, which costs some conciseness, but the structure remains clear and usable.

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?

The tool is simple, has an output schema, fully described parameters, and rich annotations. The description adds the remaining important context: delivery filtering, empty-result behavior, account prerequisite, and exclusions. Nothing material is missing for correct invocation.

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 both the child reference and the limit bound are already documented in the schema. The description reinforces the at-most-5 limit and the newest-first ordering, but it adds little parameter meaning beyond the schema.

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?

The description states a specific resource and scope: the tutor's most recent updates sent to the parent about the child, returned newest first and capped at the limit. It also specifies what is returned per update (date, type, text), which lets an agent distinguish this from general progress or report tools.

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?

It gives an explicit use case: when the parent asks what the tutor said lately. It also states clear exclusions, noting that private notes, drafts, and unsent updates are never returned, and it names the required connected SATCoach parent account.

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?