Skip to main content
Glama
Sign In
softglaze-browser-mcp

softglaze-browser-mcp

by softglazee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List groups

list_groups
Read-onlyIdempotent

Retrieve profile groups with the number of visible profiles in each, enabling read-only review of group membership and profile counts.

Instructions

Lists profile groups with how many of your visible profiles each holds. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

The trailing "Read-only" merely restates readOnlyHint and adds nothing. The genuinely useful disclosure is that counts are based on "your visible profiles," which tells the agent results are scoped/aggregated rather than raw rows; nothing about ordering, pagination, or empty-group handling is given, though annotations already cover the safety profile.

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 the substantive content (groups plus per-group counts) front-loaded. The only wasted words are "Read-only," which duplicates the annotation, but the cost is trivial.

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 zero-parameter list tool with no output schema, the description conveys what is returned: groups with profile counts, limited to visible profiles. Missing details like ordering or whether empty groups appear are minor given the tool's simplicity.

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 takes zero parameters, so there is nothing for the description to clarify about inputs; baseline applies. The description's mention of visible-profile counts does help interpret the result rather than the input.

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?

States a specific verb and resource ("Lists profile groups") and adds the meaningful detail that each group is reported with its profile count. It is distinguishable from list_profiles by the word "groups," but it never explicitly contrasts itself with that sibling.

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?

Usage is only implied by the name and verb; there is no statement of when to call this versus list_profiles, create_group, or move_profiles_to_group. An agent can infer it is the enumeration call, but nothing is spelled out.

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