Skip to main content
Glama
Sign In
edge-mcp

edge-mcp

by hualang-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

new_tab

Opens a new Edge tab and optionally navigates it to a URL, returning the tab's targetId for later control.

Instructions

Open a new tab in Edge and optionally navigate it to a URL. Returns the new tab's targetId.

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to open. Omit for a blank tab (about:blank).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the return value (targetId) and the blank-tab default. It does not say whether the new tab becomes the active/focused tab, whether it inherits the current page context, or what happens if the URL fails to load, which are the behaviors an agent would want for a tab-creating 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?

Two short sentences, front-loaded with the action and followed immediately by the return value. No filler or redundancy.

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 one-optional-parameter tool with no output schema, the description covers what it does, the default behavior, and the returned identifier, which is close to sufficient. The only meaningful omission is whether the new tab takes focus, which matters for chaining follow-up 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?

Schema coverage is 100% and the single optional parameter is fully documented in the schema, including the blank-tab default. The description only restates that the URL is optional, adding no format or validation detail beyond what the schema already provides, so the baseline 3 applies.

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?

The description gives a specific verb and resource ("Open a new tab in Edge") plus the optional navigation behavior, so the agent can tell it apart from navigate, switch_tab, and list_tabs by name alone. It stops short of explicitly contrasting with those siblings, which keeps it out of 5 territory.

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 implied rather than stated: the word "optionally" signals that omitting the URL yields a blank tab, and the sibling list makes the tab-creation role obvious. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. navigate for an existing tab).

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