Skip to main content
Glama
Sign In
Tester Agent

Tester Agent

by datb2404981
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

AI mở phiên kiểm thử trình duyệt

tester_browser_start

Launch Chromium for a registered QA project and load a specified page or viewport so a connected model can capture the live site for inspection.

Instructions

Mở Chromium theo dự án đã đăng ký. Sau đó gọi tester_browser_see để model thực sự nhìn thấy ảnh website.

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": {
      "project": "<project>"
    },
    "name": "tester_browser_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
pageNo
projectYes
viewportNodesktop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one valuable non-obvious behavior: starting the browser is necessary but not sufficient for the model to see the page. However it is silent on session lifecycle (what happens if a session is already running), permissions, and what the call returns — significant gaps for a tool that spawns a browser process.

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 required next step. No filler and no repetition of the title.

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?

For a session-initialization tool with four undocumented parameters, no annotations, and no output schema, the description is too thin. It neither explains what the call returns (session handle, current URL, status) nor how goal/page/viewport shape the opened page.

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% across four parameters, so the description must compensate and largely does not. It clarifies only that 'project' refers to a pre-registered project; 'goal', 'page', and the 'viewport' enum are left entirely unexplained in both the schema and the description.

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 names a specific verb and resource — opening Chromium for a registered project — and adds the crucial caveat that the launch alone does not give the model vision. It stops short of distinguishing this tool from other entry points such as tester_test_web, so an agent cannot fully rank it against every sibling.

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?

It establishes a clear precondition (the project must already be registered) and prescribes the immediate follow-up call to tester_browser_see, which is the real workflow guidance an agent needs. It gives no when-not guidance, no mention of alternatives, and does not say whether an already-open session should be reused.

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