AllSearch MCP

Provider health

health

Read-onlyIdempotent

Check provider configuration, circuit-breaker status, and cache counters; set probe=true to run bounded cached probes.

Instructions

Provider configuration, circuit-breaker state and cache counters. probe=true runs bounded cached probes.

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

Input Schema

Name	Required	Description	Default
`probe`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower. The description still adds real context beyond them: probes are 'bounded' (latency-limited) and 'cached' (results may be reused rather than freshly measured), which an agent needs to interpret probe output correctly.

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?

Two tight sentences with the resource contents front-loaded and the parameter behavior second. No padding, but the fragmentary first sentence is slightly ambiguous about whether it returns configuration or configures the provider, which only the readOnly annotation resolves.

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 no explanation, and the single parameter is covered by the description. Safety profile comes from annotations. What remains thin is the practical meaning of probing (cost, freshness), a minor gap for a one-parameter diagnostic tool.

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 carry the probe parameter. It explains that probe=true triggers bounded cached probes and, by contrast, implies the default (false) returns passively collected state without running probes. It compensates well for the coverage gap, though it never states the default explicitly.

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 names the exact resource and its contents: provider configuration, circuit-breaker state, and cache counters, plus the probe mode. It is a diagnostic/status read, clearly distinguishable from search, fetch, and read_result, though it is phrased as a noun list rather than a verb+resource statement.

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?

'probe=true runs bounded cached probes' implies the condition under which to enable probing versus leaving it off, which is useful. However there is no explicit when-to-use/when-not-to-use guidance, no stated cost or latency tradeoff of probing, and no alternative tool to route to.

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

Deploy Server