Skip to main content
Glama

SAT/ACT prep this week

sat_briefing
Read-onlyIdempotent

The signed-in family's EduAvenues SAT/ACT prep, per student: drills due or overdue this week, recent drill scores, past drill grades from before the move off Google Classroom (history only), practice tests taken, the weakest skills EduAvenues computed from their latest score report (missed out of seen), their score goal, and the top 3 things to do this week. For a parent, returns each enrolled child separately. Scaled practice-test scores are not included; they stay on sat.eduavenues.com.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description correctly spends its words elsewhere. It adds genuinely non-obvious traits: results are broken out per student, parents receive one entry per enrolled child, legacy Google Classroom drill grades are history-only, and scaled practice-test scores are deliberately excluded because they live on sat.eduavenues.com — that last point prevents an agent from assuming a complete score set.

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?

One dense but front-loaded sentence leads with the subject (whose data) before the enumeration, and every listed item carries information an agent would otherwise have to discover by calling. It is a long run-on list, so it is slightly heavier than ideal, but there is 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?

With no output schema and an aggregation tool spanning many data types, the description carries the return-value burden well by enumerating each section and flagging the one known omission (scaled scores). It also states the identity scope (signed-in family) and the parent/child expansion, leaving no material gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline is 4. The description correctly focuses on scope and return content instead of inventing parameter guidance.

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 names a concrete resource (the signed-in family's EduAvenues SAT/ACT prep data) and enumerates exactly what is returned: drills due/overdue, recent scores, historical grades, practice tests, weakest skills, score goal, and top 3 actions. It is clearly scoped to SAT/ACT prep, which distinguishes it in substance from a general family briefing, though it does not explicitly name a sibling to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no prerequisites, and no named alternative (e.g., family_briefing, what_to_study, my_progress). The 'this week' framing weakly implies a weekly check-in, but the agent must infer that rather than being told when this tool is the right choice.

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