Skip to main content
Glama
Sign In
msloop-mcp

msloop-mcp

by shayanline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

loop_search

Search Microsoft Loop pages and components by keyword. Retrieve matching files with titles, links, and dates.

Instructions

Search across your Loop pages and components by keyword (via Microsoft Graph). Returns matching files with their titles, web links, and last-modified dates.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return. Default: 25.
queryYesKeywords to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/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 mentions that searching is via Microsoft Graph and returns specific fields, but does not disclose behavioral traits such as authentication needs, rate limits, or that it is a read-only operation.

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 a single sentence that is front-loaded with the verb and resource. Every word adds value, and no unnecessary information is included.

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 search tool with no output schema, the description adequately explains return fields (titles, web links, last-modified dates). It does not mention pagination or result format, but overall it is fairly complete.

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 description coverage is 100%, with both parameters having descriptions. The tool description adds context about return values and the use of Microsoft Graph, but does not significantly extend 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 searches across Loop pages and components by keyword, using Microsoft Graph. It specifies the resource, action, and return information (titles, web links, last-modified dates), distinguishing it from sibling tools like loop_list_pages.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention when not to use it or compare it to similar tools like loop_list_pages or loop_get_page.

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