Skip to main content
Glama
Sign In
loop-mcp

loop-mcp

by 2mattias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

loop_create_page

Create a Microsoft Loop page and populate it with Markdown. Automates the paste-to-blocks conversion, turning your content into formatted Loop blocks.

Instructions

Create a new Microsoft Loop page and fill it with Markdown. Drives the authenticated Loop session; Markdown is auto-normalized for Loop's paste-to-blocks conversion. Requires an active session.

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": {
      "title": "<title>",
      "markdown": "<markdown>"
    },
    "name": "loop_create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesPage title.
markdownYesPage body in Markdown.
workspace_urlNoTarget workspace URL. Defaults to LOOP_DEFAULT_WORKSPACE_URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool 'drives the authenticated Loop session' (indicating stateful action), mentions markdown auto-normalization, and requires an active session. This provides valuable behavioral context beyond the schema.

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?

The description is three concise sentences, each earning its place: purpose, behavioral mechanism, and prerequisite. It is front-loaded with the core action and avoids redundancy.

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 create tool with 3 parameters and no output schema, the description is quite complete. It covers the operation, explains normalization, and notes the session requirement. It might optionally mention error cases, but overall it provides sufficient context for an agent to use it correctly.

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?

Schema description coverage is 100%, so baseline is 3. The description adds meaning to the 'markdown' parameter by explaining that it is auto-normalized for Loop's paste-to-blocks conversion, and also clarifies the 'title' parameter by saying the page is filled with Markdown. This enriches the parameter semantics 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 action ('Create a new Microsoft Loop page') and the resource ('Loop page'), and specifies that it fills the page with Markdown. This distinguishes it from siblings like loop_get_page/loop_list_pages/loop_edit_page by explicitly focusing on creation.

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 clear context for when to use it (creating a new page) and mentions the prerequisite of an active session. It does not explicitly name alternatives or exclusions, but the resource and action are specific enough to imply appropriate usage contexts.

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