Skip to main content
Glama
Sign In
Tester Agent

Tester Agent

by datb2404981
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Tester Agent kiểm thử website

tester_test_web

Scans web pages with Playwright to detect console errors, HTTP issues, and responsive layout problems across desktop and mobile viewports.

Instructions

Kiểm tra trang, console, HTTP và responsive bằng Playwright. Dùng tester_browser_* cho các luồng nghiệp vụ có thao tác và assertion.

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_test_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoscan
pageNoĐường dẫn tương đối như #/login hoặc /catalog.
projectYes
maxPagesNo
viewportsNoboth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.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 burden and largely does not. It discloses the engine (Playwright) and the check categories, but says nothing about side effects on the target site, whether authentication is required, whether the scan is read-only, or how results are delivered.

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 with zero padding: coverage first, alternative second. Every clause earns its place and the routing information is front-loaded.

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 5-parameter scanning tool with no annotations and no output schema, the description is incomplete: the required 'project' parameter and the return/report shape are unexplained. It is accurate as far as it goes but leaves an agent guessing about inputs and results.

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 only 20% — just 'page' is documented. Nothing in the description explains 'project' (the sole required parameter), 'maxPages' crawl limits, 'mode', or the 'viewports' choices, so the description does not compensate for the coverage 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?

The description names a concrete verb ('Kiểm tra') plus the exact resource set: page, console, HTTP and responsive, run via Playwright. It also distinguishes itself from the tester_browser_* family, so an agent can separate this scan tool from the interactive-flow tools. It stops short of a 5 because the object of the scan (a project's URL/pages) is only implied.

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 gives an explicit routing rule: use tester_browser_* for business flows that involve actions and assertions, implying this tool is for automated scanning. That is a real when/when-not split. It does not state prerequisites (auth, running dev server) or what to do after the scan.

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