Skip to main content
Glama

body_open_external

Opens an HTTP/HTTPS URL in the user's own browser as a new tab, using the default or Chrome, Edge, Brave, or Firefox instead of Body-MCP's controlled browser.

Instructions

Open a URL in the USER'S OWN browser (a new tab), not in Body-MCP's browser.

Use it when the task says "open it in my browser". browser: "" = the operating system default, or one of chrome | edge | brave | firefox to pick the browser explicitly. Only http/https are handed over (no shell, no command strings) and the browser executable comes from a fixed table. Body-MCP's own Chromium stays separate - it is the controlled one.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
browserNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does meaningful work: it discloses the safety boundary (only http/https, no shell or command strings, executable taken from a fixed table) and the side effect (new tab in the user's own browser). It does not say what happens on failure or whether the call blocks, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and destination, and the remaining sentences each carry useful disambiguation or safety information. The closing remark about Body-MCP's Chromium is slightly redundant with the opening contrast but still reinforces the distinction.

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 two-parameter, annotation-free tool with no output schema, the description covers the destination, the accepted browser values, the security boundary, and the separation from the controlled browser. Only error/return behavior is unaddressed, a minor gap given there is no output schema to document.

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 0% and there are no enums, so the description must compensate, and it does for the ambiguous parameter: browser "" means OS default and the accepted values are chrome | edge | brave | firefox. The url parameter is left implicit but is self-evident from the purpose.

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 specific verb and resource ('Open a URL') plus the destination ('USER'S OWN browser, a new tab') and explicitly contrasts it with Body-MCP's own browser, so an agent can tell exactly what this does and what it is not.

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?

Gives an explicit trigger phrase ('use it when the task says "open it in my browser"') and an implicit exclusion via the contrast with Body-MCP's controlled Chromium. It stops short of naming a sibling tool to use for the controlled-browser case, but the when-to-use condition is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.