Skip to main content
Glama
Sign In
edge-mcp

edge-mcp

by hualang-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

screenshot

Capture the active Edge tab as an inline PNG or JPEG image, choosing full-page or viewport, so models can inspect the page visually.

Instructions

Capture a screenshot of the active tab (full page or viewport) and return it as an image. The image is returned inline so the model can see it.

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

Input Schema

NameRequiredDescriptionDefault
formatNoImage formatpng
qualityNoJPEG quality 1-100 (ignored for PNG)
fullPageNoCapture the entire scrollable page (true) or just the viewport (false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the two most important traits – the capture is scoped to the active tab and the image is returned inline rather than as a path or URL – but says nothing about whether the operation is read-only, what happens on restricted or about:blank pages, size/latency limits, or error behavior for a tool that can return large payloads.

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, zero filler, with the core action and the output mechanism front-loaded. Nothing is repeated and nothing needs reordering.

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 zero-required-parameter capture tool with no output schema, the description correctly explains the return value ('inline so the model can see it'), which is the main thing an agent needs. It is only slightly short of complete because it does not mention tab targeting prerequisites or page restrictions.

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 description coverage is 100%, so the schema already defines format, quality and fullPage. The description's parenthetical '(full page or viewport)' merely restates the fullPage parameter and adds no format/quality guidance beyond the schema, which is the expected baseline when the schema does the work.

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 and resource ('Capture a screenshot of the active tab') plus the output form ('return it as an image'). The scope ('active tab') distinguishes it from any whole-window capture, though the description never references the surrounding navigation/click siblings by name.

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 by the phrase 'so the model can see it', which suggests reaching for it when visual inspection is needed. There is no explicit when-to-use versus alternatives (e.g. use get_text when only text is needed, or switch_tab first if a different tab is targeted).

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