Lists available browser profiles and their states on the Scalebrowser daemon, helping AI agents select a persistent-identity browser for login and page tasks.
The profiles on this daemon, with their state.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations at all, the description carries the full burden. It reveals that a state field is included in the result, but says nothing about whether stopped/inactive profiles are listed, ordering, pagination, or any auth requirement.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence with no filler and the key information (resource + scope + returned state) front-loaded. It is terse rather than padded, though it is arguably under-specified for a fragment without a verb.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A parameterless read-only list tool is simple enough that this nearly suffices, but with no output schema the description should say more about the shape of the returned list and whether the result is filtered or paged.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is no parameter semantics to document. Baseline 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Identifies the resource (profiles), the scope (on this daemon), and what is returned (their state). The verb is only implied by the tool name, but the resource is specific enough to distinguish it from siblings like profile.create, profile.start, profile.stop, and profile.update.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance and no mention of alternatives. The many profile.* siblings (create/start/stop/update/batch) make a routing sentence genuinely useful, and none is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.