Skip to main content
Glama
Sign In
Enhanced Browser MCP Server

Enhanced Browser MCP Server

by The-Thought-Magician
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_screenshot

Capture a screenshot of the current browser page for visual verification or documentation. View the rendered state of any web page during automation.

Instructions

Take a screenshot of the current page

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior1/5

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

There are no annotations, so the description carries the full burden. It only states the action itself and discloses no behavioral details such as whether the screenshot is saved to a file, returned as base64, captures the full page or viewport, or any side effects. This is essentially a tautology of the function name.

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?

The description is a single, concise sentence that is immediately clear and front-loaded. Every word earns its place with no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for the action itself but lacks crucial context about what the output or result will be. With no output schema, the agent is left wondering whether the screenshot is returned directly, stored, or requires retrieval. This is a significant gap for a tool with minimal structured metadata.

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?

The tool has zero parameters and the schema is empty. The description does not need to explain parameter semantics. Per the rubric, a score of 4 is the baseline for tools with no parameters.

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 clearly states the action ('Take a screenshot') and the resource ('current page'). It is specific and unambiguous. However, it does not distinguish this from the sibling tool browser_snapshot, which could potentially be interpreted as a similar capture operation.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives, or any exclusions. The description simply states the operation without context. For example, it does not clarify whether this should be used for visual debugging, documentation, or comparisons.

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