Skip to main content
Glama
Sign In
infinitecampus-mcp

infinitecampus-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ic_get_schedule

Read-only

Get a student's class roster: every course with its section placements, across every term of the current enrollment. Not filtered by date or term — each placement carries its own term, so narrow the result yourself.

Instructions

Get a student's class roster: every course with its section placements, across every term of the current enrollment. Not filtered by date or term — each placement carries its own term, so narrow the result yourself.

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.
districtYesDistrict name from ic_list_districts
studentIdYesStudent personID from ic_list_students

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.1.3
    • removedInput schema / properties / date
      Removed value: -{
-  "description": "YYYY-MM-DD; defaults to today",
-  "type": "string"
-}
    • removedInput schema / properties / termFilter
      Removed value: -{
-  "description": "Term name or ID; optional",
-  "type": "string"
-}
  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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely non-obvious behavior: no date/term filtering is applied and each placement carries its own term. It doesn't discuss pagination or result size, but the unfiltered-scope disclosure is the key behavioral trait here.

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?

Two tight sentences with the core resource front-loaded and the scoping caveat immediately after. No filler, no restatement of the 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?

With no output schema, the description compensates by describing the return shape (courses with section placements, each tagged with its term). Combined with readOnly annotations and fully documented params, an agent has enough to call this correctly; only result size/pagination is unaddressed.

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 the view enum, district, and studentId all thoroughly documented in the schema itself. The description adds no parameter-level detail, so the baseline of 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 ("Get a student's class roster") and enumerates the payload shape (every course with its section placements). The resource is clearly distinct from siblings like ic_list_grades or ic_list_attendance, though it never names a sibling to sharpen the boundary.

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 clear usage context: the result spans every term of the current enrollment and is deliberately unfiltered, so the caller must narrow it. It stops short of naming an alternative tool or stating when-not-to-use, so it is context rather than routing.

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