Skip to main content
Glama

pool_status

Check the current status of active browser instances and available resources in the browser pool to monitor session availability and manage concurrent usage.

Instructions

Browser pool status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that retrieves and formats the browser pool status.
    function getPoolStatus() {
      const status = [];
      for (const [port, inst] of instances) {
        status.push({
          port,
          sessionId: inst.sessionId,
          idleMinutes: Math.round((Date.now() - inst.lastUsed) / 60000)
        });
      }
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            instances: status,
            maxInstances: MAX_INSTANCES,
            thisSession: sessionId,
            assignedPort,
            hasActivePage
          }, null, 2)
        }]
      };
  • index.js:475-476 (registration)
    Registration of the 'pool_status' tool using the MCP server instance.
    server.tool('pool_status', 'Browser pool status', {},
      async () => getPoolStatus());
Behavior2/5

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

No annotations are provided, yet the description fails to disclose behavioral traits. It does not indicate this is a read-only operation, what status fields are returned, or whether the pool must be initialized first.

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?

At three words, it is appropriately brief for a parameterless status check, but it is under-specified rather than efficiently informative. It front-loads no actionable guidance.

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?

Without an output schema, the description should explain what status information is returned (e.g., available instances, utilization). Instead, it provides only a label with no behavioral or return value context.

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?

Input schema has zero parameters. Per evaluation rules, zero parameters establishes a baseline score of 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Browser pool status' is essentially a noun phrase restating the tool name with the domain prepended. It lacks a specific verb indicating what the tool does (retrieve? check? update?) and does not distinguish from sibling tool pool_test.

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

Usage Guidelines2/5

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

No guidance provided on when to use this versus pool_test or other browser management tools. No mention of prerequisites or typical use cases (e.g., health checks before operations).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OMGEverdo/browser-pool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server