Skip to main content
Glama

Coach weekly report

get_coach_weekly_report
Read-onlyIdempotent

Read the coach's stored weekly report for a completed week: team stats, flagged buckets with per-athlete reasons and a compact roster, cut to the athletes the coach still coaches and what they share. available: false with a reason means no report exists for that week or reports are not enabled for this coach; get_coach_athletes and get_team_overview give live data.

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

Input Schema

NameRequiredDescriptionDefault
weeks_agoNo0 = the latest completed week, up to 8 weeks back.

Output Schema

NameRequiredDescriptionDefault
errorNo
statsNo
headerNo
reasonNo
statusNo
bucketsNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
warningsNo
availableNo
next_stepNoWhat can be done next, for example after a failure.
report_idNo
athlete_idNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
generated_atNo
roster_totalNo
user_contentNoFields in this result that people wrote.
roster_compactNo
weeks_returnedNo
suggested_toolsNo
generated_at_isoNoThe epoch field beside it as a UTC instant; the local day can differ.
roster_truncatedNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
not_shared_athletesNo
session_definitionsNoSessions that several rows of this result share by session_ref.
content_block_fieldsNoColumn names of every content_blocks row, nested blocks rows included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / content_block_fields / description
      Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not solely responsible there. It still adds real behavioral content: this is a stored snapshot rather than live data, results are filtered to currently-coached athletes, and `available: false` with a reason signals either no report for that week or reports disabled for the coach.

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?

Two sentences, front-loaded with the core action and payload before the failure mode and alternatives. Slightly dense in the middle clause ('cut to the athletes the coach still coaches and what they share'), but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 not be explained, yet the description still outlines the report's structure and the empty-report signal. A single-parameter, annotated read tool is well covered; only a note on freshness/latency of the snapshot is arguably 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%; the single `weeks_ago` parameter is fully documented in the schema with default and 0–8 range. The description adds only the framing 'completed week,' which is contextually useful but not additional parameter semantics 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?

Names a specific verb and resource ('Read the coach's stored weekly report for a completed week') and enumerates the payload: team stats, flagged buckets with per-athlete reasons, compact roster. It also scopes the contents ('cut to the athletes the coach still coaches and what they share'), which lets an agent distinguish a stored snapshot report from the live-data siblings.

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?

Gives a clear usage condition (a completed week's stored report) and points to alternatives — get_coach_athletes and get_team_overview — for live data. It does not spell out a negative case beyond that, but the stored-vs-live routing is explicit enough to choose correctly.

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