Skip to main content
Glama
Sign In
BrowserSolver MCP Server

BrowserSolver MCP Server

Official
by browsersolver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Stats

stats
Read-only

Check infrastructure health for an API engine or endpoint over the past hour to diagnose availability issues. Access is enabled per account; an HTTP 403 means contact support.

Instructions

Stats. Infrastructure health for an engine or endpoint over the last hour. Not scoped to your account or tenant. Enabled per account: HTTP 403 means contact support to activate it.

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

Input Schema

NameRequiredDescriptionDefault
pathNoSpecific endpoint to check, for example /v1/website/screenshot. If you also pass engine, use an endpoint from that API.
engineNoAPI family to check, for example website. Provide at least engine or path.

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?

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint), and the description adds genuinely new behavior: the fixed one-hour time window, the cross-tenant/non-account scope, and the 403 activation failure mode with a remediation path. It stops short of saying what the health payload contains, which matters since no output schema exists.

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?

Three short sentences, front-loaded with scope, then the tenant caveat, then the failure mode. The only waste is the opening 'Stats.' fragment, which duplicates the title and name.

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 two-optional-parameter read tool with no output schema, the description covers the essentials an agent needs: what is measured, the time window, the scope boundary, and how to interpret a 403. Only the shape of the returned health data is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented in the schema, including the 'provide at least engine or path' constraint and the engine/path consistency rule. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 resource and scope: 'Infrastructure health for an engine or endpoint over the last hour.' The 'Not scoped to your account or tenant' line separates it from the sibling 'usage' tool without naming it, so an agent can distinguish them. The leading 'Stats.' sentence merely restates the name and adds nothing.

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?

Gives clear context for when the tool applies (engine- or endpoint-level health, one-hour window) and an explicit operational rule: HTTP 403 means the feature is not enabled and support must be contacted. It does not explicitly name 'usage' as the alternative for account/tenant-scoped data, leaving that inference to the agent.

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