Skip to main content
Glama
Sign In
Mochi

Mochi

by DevZonayed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_list_selectors

List cached browser selectors with optional origin filtering, aiding in selector management and debugging.

Instructions

List cached selectors. Pass origin to filter (defaults to current).

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

Input Schema

NameRequiredDescriptionDefault
originNo
allNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It only states that it lists cached selectors, with no mention of side effects, read-only nature, output format, or whether it mutates state. This leaves significant gaps for an agent to predict behavior.

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 description is very short (one sentence), making it concise but potentially too sparse. It front-loads the purpose but omits necessary details. It is not verbose, but the brevity limits its usefulness.

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?

Given no output schema and numerous sibling tools, the description lacks details about return values, pagination, or how to use the results. It does not explain the concept of 'cached selectors' or how this tool fits into the broader workflow. Significant gaps remain for effective tool invocation.

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?

The description explains the 'origin' parameter with a note that it defaults to current, adding meaning beyond the schema. However, the 'all' parameter is not mentioned at all. With 0% schema description coverage, the description should compensate but fails to fully explain parameters.

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 clearly states it lists cached selectors, which is a specific action. It also mentions filtering by origin. However, it doesn't elaborate on what qualifies as a cached selector, leaving some ambiguity. The tool's name and description differentiate it from siblings like browser_forget_selector and browser_recall_selector.

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 (list selectors, optionally filtered by origin) but does not explicitly state when to use this tool versus alternatives like browser_recall_selector for retrieving a single selector. It provides filtering guidance but lacks when-not or alternative recommendations.

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