Skip to main content
Glama
Sign In
infinitecampus-mcp

infinitecampus-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ic_download_document

Destructive

Download a student's document (PDF) to disk, inside the download directory (IC_DOWNLOAD_DIR, default ~/Downloads). documentId is the url field returned by ic_list_documents. Will not overwrite an existing file unless overwrite is true.

Instructions

Download a student's document (PDF) to disk, inside the download directory (IC_DOWNLOAD_DIR, default ~/Downloads). documentId is the url field returned by ic_list_documents. Will not overwrite an existing file unless overwrite is true. Returns FeatureDisabled if the district has the module turned off.

Input Schema

NameRequiredDescriptionDefault
districtYes
overwriteNo
documentIdYesThe url field returned by ic_list_documents
destinationPathYesWhere to write the PDF. Must be inside the download directory (IC_DOWNLOAD_DIR, default ~/Downloads); a relative path resolves against it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.3
    • changedInput schema / properties / destinationPath / description
      Previous value: -"Absolute path where the PDF should be written"New value: +"Where to write the PDF. Must be inside the download directory (IC_DOWNLOAD_DIR, default ~/Downloads); a relative path resolves against it."
  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.1/5.0
Behavior4/5

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

Goes beyond the annotations (destructiveHint=true, openWorldHint=true) by disclosing the key safety behavior: existing files are not overwritten unless overwrite=true, plus a named error condition (FeatureDisabled). Does not cover auth/permission requirements or what a successful result contains.

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?

Front-loaded with the action and resource, then constraints and failure mode in tight prose with no filler. Well organized into three focused sentences.

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 download tool with no output schema and annotations covering the safety profile, the description supplies the essential non-overwrite default, directory constraint, and error condition. The unexplained 'district' parameter and absence of auth details are the main residual gaps.

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 50%; documentId and destinationPath are already documented in the schema and the description largely restates them. It does add the semantics of overwrite (schema has no description for it), but the required 'district' parameter remains unexplained in both schema and description.

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?

Names a specific verb (Download) and resource (a student's document/PDF) and states the destination scope (inside IC_DOWNLOAD_DIR). It is clearly distinguishable from the sibling ic_list_documents, which enumerates rather than retrieves.

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?

Provides workflow routing by identifying documentId as the url field produced by ic_list_documents, and notes the module can be disabled (FeatureDisabled). It gives a clear precondition but no explicit exclusions or alternatives beyond that.

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