Skip to main content
Glama

Attendance

get_attendance
Read-onlyIdempotent

Retrieve a student's absences and tardies with dates, periods, classes, codes, and reasons, optionally filtered by a start and end date.

Instructions

Absences and tardies with date, period, class, code and reason, from the attendance plugin; falls back to the attendance HTML grid if the plugin is unavailable. Optionally limit to a date range (YYYY-MM-DD).

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_attendance"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date, YYYY-MM-DD
fromNoStart date, YYYY-MM-DD
studentNoStudent to use: name, or index from list_students. Defaults to PS_DEFAULT_STUDENT, else the student PowerSchool shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent non-destructive behavior, so the bar is lower, and the description still adds real value by disclosing a data-source fallback: it uses the attendance plugin and falls back to the HTML grid when unavailable. That fallback explains possible latency/format variance and is not derivable from the annotations. It does not contradict openWorldHint=true.

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 returned data shape and followed by the optional range constraint. No filler, though the fallback clause could be tightened.

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?

With no output schema, the description compensates by enumerating the returned fields (date, period, class, code, reason), and the fallback note covers reliability questions. Student selection defaults are left entirely to the schema, which documents them, so nothing critical is 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 description coverage is 100%, with both date bounds and the student default fully documented in the schema, so baseline is 3. The description only restates that the range is optional and uses YYYY-MM-DD, adding no semantics beyond structured fields.

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 resource (attendance) with concrete content enumeration: absences and tardies with date, period, class, code and reason. An agent can distinguish this from sibling grade tools like get_grades or get_missing, though the description never explicitly names an alternative.

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

Usage Guidelines3/5

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

Gives a usage hint for one parameter ('Optionally limit to a date range'), but does not say when to prefer this tool over siblings such as get_schedule or get_missing, nor does it state any exclusions or prerequisites.

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