Skip to main content
Glama
Sign In
msloop-mcp

msloop-mcp

by shayanline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

loop_login

Authenticate to Microsoft Loop silently using an existing session; opens a browser only when the session has expired. Can force a full re-login.

Instructions

Sign in to Microsoft Loop. Tries silently first (no browser); opens a browser only when the session has expired. Set force_new: true to force a full re-login.

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

Input Schema

NameRequiredDescriptionDefault
force_newNoForce a full re-login even if a session exists — clears the saved session first. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Discloses important behaviors: silent browserless attempt first, browser prompt only on expired session, and effect of force_new clearing saved session. Without annotations, this compensates well.

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 sentences are concise, front-load the action, and contain no fluff. Every phrase adds value.

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?

Given no output schema, the description adequately explains the login mechanism and parameter. However, it doesn't state that a successful login establishes a session for other tools, which is implicitly understood.

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

Parameters4/5

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

The single parameter force_new has 100% schema coverage; the description adds behavioral context ('clears the saved session first'), enhancing understanding beyond the schema.

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 clearly states the tool signs in to Microsoft Loop, specifying the silent attempt first and browser fallback on session expiry. This distinguishes it from sibling tools like loop_logout or loop_status.

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 explains when to use (sign in) and how to force a new session with force_new parameter. While it doesn't explicitly list when not to use, the guidance is clear for a login tool.

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