Skip to main content
Glama

This week for my family

family_briefing
Read-onlyIdempotent

The signed-in family's EduAvenues week, per child: upcoming live classes and practice exams (next 14 days), homework that is due, missing or reviewed (with the coach's review notes), the latest coach feedback on their writing (released scores, top strength, top priority, report link), self-paced progress with the weakest lessons, whether a coach should step in, and the top 3 things to do this week. Answers questions like "how is my child doing" and "what do we need to do this week".

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": "family_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds useful behavioral detail beyond that: the fixed 14-day lookahead window, the per-child grouping, the inclusion of coach review notes and a released-score report link, and that it surfaces a coach-intervention judgment. It does not discuss payload size, empty-family behavior, or how unreleased scores are treated.

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?

It is a single dense sentence front-loaded with the scope and then a long inventory of sections; every clause names a real data area rather than padding. It would read faster as a short bulleted list, and the trigger-question sentence is slightly long, but nothing is redundant.

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 parameters and no output schema, the description carries the full burden of telling the agent what comes back, and it does so comprehensively item by item, including the top-3 actions and the coach-intervention flag. An agent can decide to call it and set expectations for the response without any further structured metadata.

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?

There are zero parameters, so the baseline is 4. The description still adds meaningful scope context by saying the data is the 'signed-in family's' and per child, which tells the agent the tool is implicitly scoped to the authenticated account with no filters to supply.

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 opens with a specific verb-plus-resource framing ("The signed-in family's EduAvenues week, per child") and then enumerates the exact contents: upcoming live classes and practice exams in the next 14 days, homework due/missing/reviewed, coach feedback on writing, self-paced progress with weakest lessons, coach-intervention flag, and top 3 actions. This is clearly distinguishable from narrower siblings like sat_briefing or my_progress, which cover single domains.

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

Usage Guidelines4/5

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

It gives concrete trigger questions ("how is my child doing", "what do we need to do this week") plus an explicit 14-day horizon, so an agent knows which user intents select this tool. It stops short of naming when to prefer a sibling such as sat_briefing or my_writing_feedback for a focused drill-down, so no exclusion guidance is present.

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