Skip to main content
Glama

studentfirst_class_attendance

Read-only

Lists every class session with date, time, room, and attendance status so you can check missed classes or attendance for a subject.

Instructions

List every session of your StudentFirst classes with date, time, room and whether attendance was recorded as present, absent or not yet recorded. Use when the user asks which classes they missed or the attendance of one subject.

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

Input Schema

NameRequiredDescriptionDefault
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.
classCodeNoA subject code ("AB1001") or class code ("AB1001-TA"); omit for all classes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavior detail by listing the three attendance states, including 'not yet recorded,' but says nothing about result volume, pagination, or what happens to sessions with no record — minor gaps for a tool that returns 'every session'.

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 tightly written sentences with the returned data front-loaded and the usage cue second. No filler or redundant restatement of the tool name.

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?

For a simple read-only tool with two optional, fully documented parameters and no output schema, the description covers the essentials and usefully enumerates return fields. Only result-size and pagination behavior is left unstated.

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% and both parameters are well documented in the schema, including the account cross-reference and the AB1001 / AB1001-TA code formats. The description only implies the subject-filtering behavior via 'attendance of one subject,' adding little beyond the schema — baseline 3 applies.

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?

States a specific verb and resource — list every session of StudentFirst classes — and enumerates the returned fields (date, time, room, attendance status). It is clearly distinct from the other studentfirst_* tools, though it doesn't name a sibling explicitly to anchor the difference.

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 concrete triggering scenarios: 'when the user asks which classes they missed or the attendance of one subject.' This maps the second use case onto the classCode parameter. No explicit when-not-to-use or named alternative is provided, but the usage context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.