Skip to main content
Glama

status

Check whether one pooled Chrome browser is healthy, or list all browsers with their state, holder, and expiry—without needing a lease and without exposing endpoints.

Instructions

Prove one browser healthy, or list every browser with its state, holder and expiry. Needs no lease and never shows an endpoint.

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

Input Schema

NameRequiredDescriptionDefault
browserNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden and does reasonably well: it discloses that no lease is required and that endpoints are never exposed, both non-obvious and operationally relevant traits. It signals read-only semantics through the verbs 'prove' and 'list.' It stops short of stating idempotency or side-effect guarantees explicitly, but the gap is small.

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 sentences, both front-loaded with the primary mode first and the enumeration mode second, followed by two negative constraints. No filler wording; every clause adds information an agent needs.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the key returned fields (state, holder, expiry). For a one-optional-parameter inspection tool this is nearly complete; the main omission is how browsers are identified and what a failed health proof looks like.

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?

Schema description coverage is 0%, so the description must compensate for the single optional 'browser' parameter. It does: the conditional phrasing makes clear that providing a browser targets one browser while omitting it enumerates all, which is the key semantic the schema cannot convey. Exact accepted identifier format (name vs id) is left unstated.

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 uses specific verbs and resources: 'prove one browser healthy' and 'list every browser with its state, holder and expiry.' An agent can tell this is a read-only inspection tool. It doesn't explicitly name lease/release as siblings, relying instead on 'Needs no lease' to distinguish itself, which is softer than naming the alternative.

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 'or' construction implies argument-conditional usage: supply a browser to check one, omit it to enumerate all. 'Needs no lease' hints that no prerequisite acquisition step is required. However, there is no explicit when-to-use guidance relative to lease/release, and no stated exclusions or conditions for choosing this over those tools.

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