Skip to main content
Glama

Child's focus areas and breakthroughs

get_focus_areas
Read-onlyIdempotent

The child's weak skills as the parent portal shows them: needsFocusedAttention (up to 2 skills the portal says need focused attention) and weakestSkills (up to 6, the portal's weakest skills, weakest first). Also up to 3 focus areas, the first of those skills, each with what goes wrong and what SATCoach does about it, in plain words, and up to 3 recent breakthroughs: mistakes the child used to make and has since fixed. For when the parent asks what the child struggles with or should work on, or whether anything is improving. Not for getting the questions the child missed or the answers: those are never returned. It doesn't explain a skill or write practice for it. 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_focus_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
childNoThe child's reference, from the list of the parent's children. Optional when the parent has one child on SATCoach.

Output Schema

NameRequiredDescriptionDefault
asOfYes
childYes
labelYes
sourceYes
summaryYes
parentUrlYes
focusAreasYes
breakthroughsYes
weakestSkillsYes
needsFocusedAttentionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only, idempotent annotations, it discloses result caps (2, 6, 3, 3), ordering (weakest first), the plain-language framing of each focus area, that raw questions/answers are never returned, and the prerequisite of a connected SATCoach parent account.

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 the returned fields and then the when-to-use/exclusions order, which is good structure. Slightly repetitive in the parentheticals — e.g. 'needsFocusedAttention (up to 2 skills the portal says need focused attention)' restates the field name.

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 exists so return values need no explanation; the description still covers caps, ordering, scope boundaries, and the account prerequisite. Nothing an agent needs to call this 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?

The single `child` parameter is fully documented in the schema (100% coverage) including its optionality and provenance from the children list, and the description adds nothing about it. With high schema coverage the baseline of 3 is appropriate.

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 (the child's weak skills, focus areas, breakthroughs) and enumerates its parts: needsFocusedAttention, weakestSkills, focus areas, recent breakthroughs. It also marks its boundaries against siblings by saying it is not the missed questions/answers and does not explain or write practice for a skill.

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 an explicit trigger — 'when the parent asks what the child struggles with or should work on, or whether anything is improving' — plus exclusions for the missed-question data and for skill explanation/practice authoring, which routes the agent to other siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources