IE Student MCP

Overview Schema Source Related Servers Discussions Admin

connects_courses

Read-onlyIdempotent

Lists available courses in IE Connects with pagination controls. Directs to Blackboard tools for readings, assessments, and grades.

Instructions

List Connects courses. For LMS readings, assessments and grades use Blackboard tools.

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": "connects_courses"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

Name	Required	Default
`ok`	No
`data`	No
`error`	No
`message`	No
`service`	No	local
`warnings`	No
`truncated`	No
`next_action`	No
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds domain context about Connects versus Blackboard but no extra behavioral details such as pagination behavior or result ordering. Given the annotations, this is a neutral score.

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 short, purposeful sentences with no filler. The core operation is front-loaded, and the second sentence adds a useful routing qualifier without redundant detail.

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 simple read-only listing tool with two obvious pagination parameters and an existing output schema, the description plus annotations are largely sufficient. It could be slightly more explicit about when to prefer connects_courses over connects_course or blackboard_courses, but nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain limit or offset at all. The parameter names, defaults, and constraints in the schema carry the meaning, but the description itself contributes no parameter-level value, falling short of what is needed when schema descriptions are absent.

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?

Description states a specific verb ('List') and resource ('Connects courses'), immediately clarifying what the tool does. It also differentiates from Blackboard tools, helping the agent distinguish it from siblings like blackboard_courses and connects_course.

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?

The description explicitly says to use Blackboard tools for LMS readings, assessments, and grades, which is a clear exclusion and points the agent to alternatives. It does not explicitly mention connectors like connects_course for detail views, but the list-oriented verb and the Blackboard routing note give adequate context.

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