Skip to main content
Glama
Sign In
msloop-mcp

msloop-mcp

by shayanline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

loop_get_page

Read a Microsoft Loop page's content as Markdown or HTML. Provide the page ID from list results to export the page content in the chosen format.

Instructions

Read the content of a Loop page as Markdown. Pass the page id from loop_list_pages. Loop pages are rich Fluid documents exported to HTML, so some interactive components may render approximately.

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

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format. Default: markdown.
page_idYesThe page id to read.

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?

Discloses that Loop pages are rich Fluid documents exported to HTML and interactive components may render approximately, informing the agent about potential lossiness. No annotations exist, so the description carries the burden well. Could mention idempotency, but read operation is implied.

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 sentences, each purposeful: purpose, usage hint, behavioral note. No wasted words. Front-loaded with the main action.

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 read tool with 2 parameters and no output schema, the description covers purpose, usage source, and a key limitation. Minor gap: no error case info, but overall complete enough given sibling tools and simplicity.

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 already provides full descriptions for both parameters (100% coverage). The description adds no additional meaning beyond what the schema offers. Baseline 3 is appropriate.

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 it reads content of a Loop page as Markdown, with a specific verb and resource. It also references getting the page id from loop_list_pages, distinguishing it from sibling tools.

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?

Provides clear context: pass page id from loop_list_pages. Implicitly tells when to use this tool (after listing pages). Lacks explicit when-not or alternative tools, but the guidance is sufficient.

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