Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

evaluate

Run custom JavaScript in a specified browser tab's main world to inspect or modify page state and automate interactions.

Instructions

Execute JavaScript in page MAIN world

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": {
      "code": "<code>"
    },
    "name": "evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
tabIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the important MAIN-world execution context, but says nothing about whether a return value is serialized back, async/promise handling, error behavior, or the security implications of arbitrary code execution in the page context.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, so there is no verbosity problem. However, brevity here comes at the cost of under-specification for a high-risk code-execution tool rather than genuine efficiency.

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?

This is an arbitrary-JavaScript execution tool with no annotations, no output schema, and 0% parameter description coverage, so the description must carry nearly all context. It provides only the execution world and omits return values, error handling, tab targeting, and safety considerations, leaving the definition substantially incomplete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no parameter meaning. 'code' is self-evident, but 'tabId' is undocumented: the description does not say whether it is required, what the default tab is, or how it interacts with the active tab. The description does not compensate for the schema gap.

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 ('Execute JavaScript') plus the execution context ('page MAIN world'), which is enough for an agent to know this runs script in the page rather than in an isolated content-script world. It does not explicitly distinguish itself from siblings like click/fill/navigate, but among the listed tools it is the only script-execution entry, so confusion risk is low.

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?

There is no when-to-use or when-not-to-use guidance, no mention of preferring dedicated tools (click, fill, navigate) over raw script execution, and no preconditions such as the page being loaded. The agent must infer all usage context.

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