IE Student MCP Free

Overview Schema Source Related Servers Discussions Admin

ie_login_start

Initiate IE/Microsoft SSO sign-in for a selected service by opening or reusing a dedicated browser, where you manually enter your password and MFA. Returns immediately without handling credentials.

Instructions

Open/reuse the selected browser for IE/Microsoft SSO only when the user wants to sign in. Returns immediately. Password/MFA input is human-only in that browser. Does not accept credentials or arbitrary URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>"
    },
    "name": "ie_login_start"
  }
}

Input Schema

Name	Required	Description	Default
`service`	Yes

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 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important runtime behavior: it returns immediately, requires human interaction for password/MFA, and will not accept credentials or arbitrary URLs. This helps the agent set correct user expectations and avoid misuse.

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 concise, front-loaded sentences each carry meaningful information: purpose, immediate return behavior, and human-only credential handling. There is no filler or redundant restatement of the tool name.

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?

For a single-parameter login-start tool with annotations and an output schema, the description covers the essential context: when to use it, what happens during the call, and important limitations. Nothing critical is missing for an agent to invoke it correctly.

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?

The schema has 0% description coverage, and the description does not explain the required 'service' parameter or how its enum values (connects, blackboard, careers) map to the SSO login flow. The enum values are self-explanatory by name, but the description leaves the parameter's role implicit rather than compensating for the missing schema descriptions.

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 action ('Open/reuse the selected browser'), a target context (IE/Microsoft SSO), and a limiting condition ('only when the user wants to sign in'). It also distinguishes itself from credential-injecting tools by stating it does not accept credentials or arbitrary URLs.

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 gives an explicit condition for use: only when the user wants to sign in. It also clarifies what the tool is not for by stating that password/MFA input is human-only and credentials/URLs are not accepted, though it does not name an alternative sibling tool directly.

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

Deploy Server