Skip to main content
Glama
Sign In
msloop-mcp

msloop-mcp

by shayanline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

loop_create_workspace

Create a new shared Loop workspace by providing a display name. Provisioning may require some time after creation.

Instructions

EXPERIMENTAL: Create a new shared Loop workspace. Workspace creation is only partially documented and the new workspace may need a moment to finish provisioning in the Loop app. Creating page content is not supported.

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": {
      "name": "<name>"
    },
    "name": "loop_create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name for the new workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Despite no annotations, the description discloses critical behavioral traits: experimental status, incomplete documentation, asynchronous provisioning delay, and unsupported page creation. This goes beyond a simple 'create' action and sets proper expectations.

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, concise and front-loaded with the important 'EXPERIMENTAL' label. No redundant information.

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 creation tool with one parameter and no output schema, the description covers experimental nature, provisioning delay, and unsupported features. It is sufficiently complete for its complexity.

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 100% with a single parameter 'name' already described in the input schema. The description adds no additional meaning or context beyond the schema's 'Display name for the new workspace.'

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 clearly states 'Create a new shared Loop workspace', which is a specific verb+resource combination. It distinguishes from sibling tools like loop_list_workspaces (list) and loop_get_page (page retrieval).

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?

Description explicitly labels the tool as 'EXPERIMENTAL' and notes that workspace creation is only partially documented, may need provisioning time, and page content creation is not supported. This provides clear context on when and how to use it, though no explicit alternatives are mentioned.

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