Weekly Report Checker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_missing_reportsB | Check who hasn't submitted their weekly reports yet |
| check_person_reportB | Check if a specific person has submitted their weekly report |
| get_submission_statsB | Get statistics about weekly report submissions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check_reports_prompt | Prompt to check who hasn't submitted their weekly reports |
| check_person_prompt | Prompt to check a specific person's report status |
| get_stats_prompt | Prompt to get statistics about weekly report submissions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_report_status | Get the current status of weekly report submissions |
| get_report_stats | Get statistics about weekly report submissions |
| get_all_members | Get a list of all team members who should submit reports |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: checking missing reports (broad), checking a specific person's report (targeted), and getting submission statistics (aggregate). There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern (check_missing_reports, check_person_report, get_submission_stats) with clear, descriptive verbs and nouns. The naming is uniform and predictable throughout.
With 3 tools, the server is well-scoped for its purpose of managing weekly report submissions. Each tool serves a distinct and necessary function without being overly sparse or bloated.
The tools cover the core read-only operations for checking and analyzing report submissions effectively. A minor gap exists in write operations (e.g., submitting or updating reports), but agents can likely work around this for the stated checking purpose.