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

softglaze-browser-mcp

by softglazee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Workspace summary

workspace_summary
Read-onlyIdempotent

Returns a read-only snapshot of profiles, groups, proxies, running profiles, plan limits, token scope, group limits, and approval settings so you can verify workspace access and capacity before use.

Instructions

Counts of profiles, groups and proxies you can see, running profiles, the plan and its limits, this token's scope and group limit, and the approval settings. Read-only. Call this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description's real contribution is disclosing the returned content — plan limits, this token's scope and group limit, approval settings — which matters because there is no output schema. A minor redundancy is restating 'Read-only', but it does not conflict with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense enumerative sentence plus two short directives; the operative instruction 'Call this first' is placed last but is short enough to be found immediately. The noun list is compact, though the long run-on enumeration slightly reduces scannability.

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?

With no output schema and no parameters, the description carries the full burden of describing what comes back, and it does so field-by-field. It omits response format or size details, but for a small summary payload that is a minor gap against what is already stated.

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 the baseline is 4. The description does not need to explain inputs, and it usefully notes that results are scoped to 'you can see' and to 'this token', clarifying the implicit authorization boundary of the results.

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 names the resource (workspace) and enumerates the specific aggregates returned: profile/group/proxy counts, running profiles, plan limits, token scope and approval settings. This distinguishes it from item-listing siblings like list_profiles or list_proxies, which return entities rather than counts. It is not a single crisp verb, but the content is specific enough for an agent to know exactly what it gets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' gives an explicit sequencing instruction that most definitions lack, telling the agent to orient with this tool before other calls. It does not name exclusion cases or explicit alternatives, so it stops short of a full when/when-not statement.

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