Skip to main content
Glama
Sign In
infinitecampus-mcp

infinitecampus-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ic_get_features

Read-only

List the district's displayOptions feature-flag allow-list for each of a student's enrollments. Each enrollment's features object is a map of ~90 flag names (attendance, behavior, assessment, documents, grades, schedule, etc.) to…

Instructions

List the district's displayOptions feature-flag allow-list for each of a student's enrollments. Each enrollment's features object is a map of ~90 flag names (attendance, behavior, assessment, documents, grades, schedule, etc.) to booleans. A false value means the district has that feature disabled for this enrollment; true or missing means it's available. An enrollment whose flags could not be fetched carries error instead of features. Used internally by other tools to short-circuit disabled features, but exposed here so the LLM can answer capability questions directly.

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.
districtYes
studentIdYesStudent personID from ic_list_students

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Addedv2.8.3

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses substantial behavior: the features object is a map of ~90 named flags to booleans, that false means disabled while true/missing means available, and that a failed fetch yields an `error` field instead of `features`. This is exactly the value-add the annotations do not provide.

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?

Purpose is front-loaded, and every subsequent sentence earns its place by explaining flag vocabulary, boolean semantics, and error handling. No filler or redundancy.

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?

With no output schema, the description fully carries the burden of describing the return shape (features map, error alternative) and the meaning of values. An agent has everything needed to call it and interpret the result.

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 67%, and the description adds no parameter-level meaning: it never explains `view`, `district`, or how `studentId` maps beyond the schema's own note. The structured schema already documents view and studentId, so this sits at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (List) and a precise resource (the district's displayOptions feature-flag allow-list) scoped per enrollment of a named student. This clearly differentiates it from the sibling list/get tools covering schedules, grades, attendance, etc.

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?

It explains the intended use case: 'exposed here so the LLM can answer capability questions directly,' and notes it is used internally to short-circuit disabled features. That gives clear context for when to reach for it, though it stops short of naming an alternative when capability info is not needed.

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