Skip to main content
Glama

health_check

Verifies Perplexity authentication, Cloudflare access, search input, source triggers, model selector hydration, and writable directories, saving an HTML+PNG diagnostic snapshot when a check fails.

Instructions

Quick (~5s) diagnostic check verifying Perplexity authentication, absence of Cloudflare blocks, composer search input, add/sources trigger, model selector hydration, and writable local directories. Saves a diagnostic HTML+PNG snapshot automatically if any check fails.

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

Input Schema

NameRequiredDescriptionDefault
profileNoOptional browser profile name or directory path for isolated/concurrent execution (e.g. 'default', 'worker-2'). When omitted, automatically routes to an idle slot in PERPLEXITY_PROFILE_DIRS / default profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses ~5s runtime, the checks performed, and a side effect: automatic HTML+PNG snapshot saving on failure. It does not state permissions or success output, but covers key behavior.

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, front-loaded with purpose and duration, then checks and side effect. No redundant wording.

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 one-parameter diagnostic tool with no output schema or annotations, the description covers what is checked and the failure side effect. It omits return-value format and explicit usage triggers, leaving minor gaps.

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 coverage is 100% and the single optional profile parameter is fully documented in the schema. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific diagnostic check and enumerates the verifications (authentication, Cloudflare blocks, composer input, add/sources trigger, model selector, writable directories), making it clearly distinct from search/login siblings.

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?

Implies diagnostic use through 'diagnostic check' and the quick duration, but does not explicitly say when to run it (e.g., before searches or after auth failures) or when to prefer login/search_advanced. No exclusions are given.

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