SATCoach: AI SAT Tutor

Child's published diagnostic report

get_diagnostic_report

Read-onlyIdempotent

The latest published summary of the child's diagnostic test, with the date it was published. If none is published yet, it returns status not_published and no results: the report isn't ready. For when the parent asks what the diagnostic said. Not for getting the diagnostic's questions, answers, or question-by-question results: it returns only the published summary, never drafts or unpublished results. 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_diagnostic_report"
  }
}

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
`report`	No
`source`	Yes
`status`	Yes
`summary`	Yes
`parentUrl`	Yes
`publishedOn`	No

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 empty-state contract: status not_published with no results when nothing is published, and that drafts or unpublished results are never returned. The only gap is it doesn't discuss return shape or latency, which the output schema largely covers.

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 empty-state behavior are front-loaded, then the exclusions and auth requirement follow. Slightly redundant between "returns only the published summary" and the earlier "latest published summary," but every clause carries information.

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 one-parameter read tool with a full output schema and safety annotations, the description covers the happy path, the not_published case, the exclusion of drafts, and the account prerequisite. Nothing needed to call it correctly is missing.

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 single child parameter is already documented in the schema, including its optionality when the parent has one child. The description adds no further parameter meaning, so the 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?

The description gives a specific verb and resource ("latest published summary of the child's diagnostic test") plus the scoping detail (published only, includes publication date). It is clearly separable from siblings like get_child_summary or get_focus_areas, which cover different data.

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 states the triggering situation ("when the parent asks what the diagnostic said") and explicitly excludes adjacent needs ("Not for getting the diagnostic's questions, answers, or question-by-question results"). It also names the prerequisite of a 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?