Skip to main content
Glama
Sign In
SuperDev

SuperDev

by Xsxdot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

List browser targets

list_browser_targets
Read-only

List local frontend deployments with web entrypoints, enabling browser control and inspection for automation tasks.

Instructions

Return local frontend deployments configured with web entrypoints.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The description adds selection criteria ('local', 'configured with web entrypoints') beyond the readOnlyHint annotation, which is useful. However, it does not disclose behavior such as return format, pagination, or filtering capabilities, so it provides only moderate additional transparency.

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 immediately states the action and scope. Every word contributes value, with no filler or redundancy.

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 simple parameterless listing tool with no output schema, the description sufficiently conveys the purpose and scope. It could be more complete by mentioning what specific fields are returned (e.g., names, URLs), but given the simplicity of the tool, it is largely adequate.

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, so the schema does not need explanation. The description adds meaning by clarifying that 'browser targets' are local frontend deployments with web entrypoints, which helps the agent understand what the tool returns without any parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Return' and a clear resource 'local frontend deployments configured with web entrypoints', which precisely defines what browser targets are. It distinguishes itself from siblings like list_services and list_debug_browsers by focusing on frontend deployments with web entrypoints.

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 when a list of local frontend deployments is needed, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. Context from sibling names (e.g., list_debug_browsers) suggests differentiation, but the description itself lacks direct guidance.

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