Skip to main content
Glama
Sign In
LemonMCP

LemonMCP

Official
by lemonXGroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

open_web_page

Opens an HTTP or HTTPS URL in Lemon's embedded WKWebView for in-app browsing and web content access.

Instructions

Opens an HTTP or HTTPS URL inside the Lemon iOS app's embedded WKWebView.

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

Input Schema

NameRequiredDescriptionDefault
urlYesHTTP or HTTPS URL to open inside Lemon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a meaningful behavioral trait: the page renders in an embedded WKWebView inside the iOS app rather than an external browser. However, it is silent on error behavior for invalid/non-HTTP URLs, whether an existing page is replaced, and what the call returns.

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?

A single tight sentence with zero waste; the action verb and target environment are front-loaded.

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?

For a one-parameter tool with no output schema, the description covers the essentials of what happens and where. It stops short of describing navigation side effects (page replacement, history) or failure modes, leaving the agent to guess at behavior on repeat or invalid calls.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents the url field including its HTTP/HTTPS constraint and 4096-char limit. The description merely restates the accepted schemes, adding no format or example detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Opens') and resource (HTTP or HTTPS URL) and locates the action precisely ('inside the Lemon iOS app's embedded WKWebView'), which separates it from sibling navigation tools like refresh_web_page or close_web_page. It does not explicitly name those siblings, but the verb/resource pair is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the entry point that must precede refresh_web_page, go_back_web_page, or close_web_page, but the description never says so. There is no statement of when to use this versus the other WebView tools, nor any exclusion criteria.

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