semester_snapshotFetch a complete overview of all active courses—including grades, missing work, deadlines, and unread counts—in a single call at the start of a session.
Get every active course in one call with its grade, missing work, upcoming deadlines and unread counts. Read-only but uses many API calls; best at the start of a session. Use course_health_check for one course.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds useful non-annotation context—that it spends many API calls, which matters for cost-aware planning. It does not cover rate-limit behavior or result pagination, so it is strong but not complete.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with what is returned, followed by cost and session guidance, then the alternative. Every sentence carries distinct information and none repeats itself.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, the description supplies the return contents, the cost profile, and the session-start recommendation. An agent has everything needed to decide to call it and to interpret what comes back.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and there is nothing to document, which is the baseline-4 case. The description does not need to compensate for any schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and a concrete resource ('every active course') and enumerates the returned payload: grade, missing work, upcoming deadlines and unread counts. It also names the sibling course_health_check and scopes itself to the multi-course case, so an agent can distinguish it from that tool without opening either schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit when-to-use ('best at the start of a session') and an explicit alternative ('Use course_health_check for one course'). The condition that selects the sibling is stated, leaving nothing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.