Skip to main content
Glama
Sign In
msloop-mcp

msloop-mcp

by shayanline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

loop_list_workspaces

List all accessible Microsoft Loop workspaces, including your personal workspace, and retrieve each workspace's ID and title.

Instructions

List all Microsoft Loop workspaces you can access, including your personal "My workspace". Returns each workspace id and title.

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_list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the return fields but omits behavioral details like potential network calls, limits, or side effects. Minimal disclosure beyond purpose.

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?

Single sentence, no wasted words. Efficiently conveys purpose and output.

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?

No output schema exists, but description explains the return format (id and title). For a simple list tool, this is sufficient. Missing details on pagination or limits, but complexity is low.

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 tool has zero parameters; description adds value by stating that no input is needed and what is returned (id and title, including My workspace). This compensates for the lack of schema complexity.

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 action ('List'), the resource ('Microsoft Loop workspaces'), the scope ('all you can access, including your personal 'My workspace''), and the output ('workspace id and title'). This distinguishes it from sibling tools like loop_create_workspace.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing workspaces but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, but the context of siblings makes the use case clear.

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