Skip to main content
Glama
Sign In
infinitecampus-mcp

infinitecampus-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ic_list_attendance_events

Read-only

Retrieve a student's attendance events—absences, tardies, early releases—with codes, excuse reasons, and comments. Filter by date range or excused-only status.

Instructions

List individual attendance events (absences, tardies, early releases) for a student. Each event has a code, description, excuse reason, and optional human-readable comments. Auto-resolves enrollmentID from the student record. Use since/until to filter by date and excusedOnly to show only excused events.

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns Infinite Campus's payload untouched. No field projection: this server has no verified record of which Infinite Campus fields matter, and inventing one would risk dropping a field a caller needs.
sinceNoYYYY-MM-DD; include only events on or after this date
untilNoYYYY-MM-DD; include only events on or before this date
districtYes
studentIdYesStudent personID from ic_list_students
excusedOnlyNoOnly include events with excuse=E

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.2.1
    • addedInput schema / properties / since / format
      Added value: +"date"
    • addedInput schema / properties / since / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • addedInput schema / properties / until / format
      Added value: +"date"
    • addedInput schema / properties / until / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
  2. Changed1 schema field changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv2.8.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuine behavioral detail beyond the structured fields: enrollmentID is auto-resolved from the student record, so the caller need not supply it. It does not discuss pagination, result volume, or error behavior for a read that can return long event histories.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and event types, then return payload, then filters. No filler and no repetition of schema text beyond what is needed for orientation.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by naming the fields each event carries (code, description, excuse reason, optional comments). Combined with the filter guidance and the auto-resolution note, an agent has enough to call this correctly for a 6-parameter read tool.

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 83%, so the schema already documents since, until, view, studentId, and excusedOnly. The description restates the same since/until and excusedOnly semantics with no added syntax, defaults, or edge-case behavior (e.g., inclusive bounds, interplay with view). Baseline 3 is appropriate when the schema does the heavy lifting.

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 individual attendance events') and enumerates the event types (absences, tardies, early releases), which concretely describes what comes back. It does not explicitly name the sibling it differs from, though 'individual events' implicitly separates it from ic_list_attendance.

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 concrete usage for two parameters ('use since/until to filter by date and excusedOnly to show only excused events'), which implies the narrowing workflow. However, it never states when to prefer this tool over ic_list_attendance or other attendance-related siblings, and there are no exclusions or prerequisites beyond the implicit studentId.

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

Deploy Server

Other Tools