Skip to main content
Glama
Sign In
google-surf-mcp

google-surf-mcp

by HarimxChoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

MCP Health Check

health
Read-onlyIdempotent

Check server status, cascade mode, rate-limiter queue size, CAPTCHA counts, cache size, and config to diagnose failing or empty searches and decide when to reduce search volume.

Instructions

MCP server status: cascade mode + transitions, rate-limiter usage, cache size, config. Call this if searches start failing or returning empty -- check cascade.totalCaptchas and rateLimiter.queueSize, and reduce search volume if they are high.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
poolNo
cacheNo
errorNo
configNo
cascadeNo
versionNo
researchNo
telemetryNo
orcarouterNo
rateLimiterNo
selfHealingNo
nativeBrowserNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.5
    • addedOutput schema / properties / orcarouter
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changedv1.1.3
    • addedOutput schema / properties / error / properties / cancel_reason
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / error / properties / phase
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / error / properties / request_id
      Added value: +{
+  "type": "string"
+}
  3. Changed1 schema field changedv1.0.4
    • addedOutput schema / properties / nativeBrowser
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  4. Changed1 schema field changedv1.0.0
    • addedOutput schema / properties / research
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  5. Addedv0.6.5
  6. Removedv0.6.1
  7. Changed3 schema fields changedv0.5.6
    • addedOutput schema / properties / pool
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / selfHealing
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / telemetry
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  8. Addedv0.5.2
  9. Removedv0.5.1
  10. Addedv0.4.8
  11. Removedv0.4.7
  12. Addedv0.3.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: which counters indicate saturation (cascade.totalCaptchas, rateLimiter.queueSize) and the recommended remediation of reducing search volume. It omits any note on cost or side effects, but there are none to disclose for a read-only status call.

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, zero filler. The capability statement comes first and the diagnostic trigger plus remediation follow, so an agent scanning the first clause already knows what the tool is.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only health check with both annotations and an output schema, the description covers the remaining burden: when to call it and how to interpret the key counters. Nothing an agent needs in order to invoke it correctly is missing.

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 schema baseline is a 4 and there is no parameter semantics to explain. The named fields (cascade.totalCaptchas, rateLimiter.queueSize) describe return values rather than inputs, which is a bonus given an output schema is already present.

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 states a concrete resource and enumerates what it reports: cascade mode and transitions, rate-limiter usage, cache size, and config. That is specific enough to separate it from the search/extract siblings, though the opening is a noun phrase ('MCP server status') rather than an explicit verb+resource construction.

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 an explicit trigger -- 'Call this if searches start failing or returning empty' -- which is a clear when-to-use condition an agent can act on. It does not name a when-not or an alternative diagnostic tool, but for a zero-param health endpoint there is no meaningful competing sibling.

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