Skip to main content
Glama
Sign In
loremotion-mcp

loremotion-mcp

by Dkpiec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

loremotion_probe_ui

Inspect current UI labels and fields, then save a screenshot to adjust selectors when the website changes.

Instructions

Inspect the current LoreMotion UI labels/fields and save a screenshot. Useful when the website changes and selectors need adjustment.

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": "loremotion_probe_ui"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathnameNo/generate/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Describes the primary action as inspection and discloses the screenshot side effect, which is important since no annotations exist. However, it doesn't specify where the screenshot is saved, whether any state is modified, or whether authentication is required.

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, front-loaded with the action and immediate purpose, with no redundant detail. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Low-complexity tool with one optional parameter and no output schema. The description covers the intent and triggering condition, but omits what pathname does and what the screenshot/output looks like, so it is not fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the pathname parameter or its default. With only one optional parameter, this is a clear gap; the agent must infer meaning from the schema alone.

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?

States a clear verb ('Inspect') and resource ('LoreMotion UI labels/fields') plus the side effect of saving a screenshot. This differentiates it from siblings like generate_video, download_video, list_history, and auth_status, which perform entirely different actions.

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?

Explicitly states when it is useful: when the website changes and selectors need adjustment. It does not offer exclusions or name alternatives, but the use case is specific enough to guide selection.

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