Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getBrowsers

List available browsers and platforms for testing, optionally filtering by web or mobile type to identify compatible test environments.

Instructions

Get list of available browsers and platforms for testing. Optionally filter by type (web or mobile).

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter browsers by type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/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 and it discloses very little: "available" and "get" imply a read-only reference lookup, but it says nothing about whether the list is global or account-scoped, whether it changes over time, or what the returned entries contain. For a low-risk read tool this is a modest gap rather than a dangerous one, but the description adds essentially no behavioral context.

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, no filler, with the core purpose front-loaded before the optional filter. Every phrase carries information and nothing could be removed without loss.

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

Completeness3/5

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

For a one-optional-parameter listing tool with no output schema, the description covers purpose and filtering but leaves the return value underspecified beyond "list of browsers and platforms". Adequate to call correctly, but thin on what the agent will actually receive.

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% and the single enum parameter is fully documented in the schema, so the baseline of 3 applies. The description restates the filter ("type (web or mobile)") but adds no meaning beyond the enum already declared, such as what the unfiltered default returns.

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 states a specific verb and resource ("Get list of available browsers and platforms") plus the purpose ("for testing"), so an agent knows exactly what it enumerates. It does not distinguish this from the sibling getDevices, which an agent could reasonably confuse with browser/platform enumeration.

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?

The description implies usage through "Optionally filter by type (web or mobile)", which tells the agent the parameter is optional and what the values mean. It gives no explicit when-to-use or when-not guidance and never points to or away from alternatives such as getDevices.

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