Skip to main content
Glama

open

Destructive

Launch a web page, mail draft, or file in its default macOS app by supplying one URL or existing path; rejects apps, executables, installers, scripts, and bundles.

Instructions

Open a web page, an email draft or a file in its default app. Give exactly one of 'url' (http, https or mailto) or 'path' (a file or folder that exists). Apps, executables, installers, scripts and bundles are refused.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA URL that starts with http://, https:// or mailto:.
pathNoAbsolute path of a file or folder. A path with ~ also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=false), the description discloses that input is handed to the OS default application and that executable-type inputs are rejected — useful safety context that explains the destructive profile. It does not explain what side effects or failure modes to expect when a page or file actually launches, which keeps it from 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.

Conciseness5/5

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

Two sentences, front-loaded with the action and resources, followed by the cardinality rule and the refusal constraint. Nothing is padded and no clause could be removed without losing a constraint.

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 tool with full schema coverage, existing annotations, and no output schema, the description covers action, input selection, and rejection rules adequately. Minor gaps remain around error behavior and whether the call blocks until the app returns, but nothing essential to invoking it is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot express: the two parameters are mutually exclusive and exactly one must be supplied, while the schema leaves 'required' empty and defines no oneOf. That is genuine semantic value beyond the structured fields.

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?

Names a specific verb (Open) and the exact resources (web page, email draft, file) plus the launch mechanism (default app). No sibling tool in the catalog opens URLs or files, so an agent can distinguish it on the name and first clause alone.

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 a clear selection rule — exactly one of 'url' or 'path' — and an explicit exclusion list (apps, executables, installers, scripts, bundles are refused), which is real guidance about when the call will fail. It does not name alternative sibling tools for cases that fall outside its scope, so it stops short of a 5.

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