Skip to main content
Glama
flin-google-search-console-mcp

flin-google-search-console-mcp

by flin-agency

health_check

Read-onlyIdempotent

Verifies local configuration and saved sign-in status without opening a browser or contacting Google, so you can confirm setup before querying Search Console.

Instructions

Check local configuration and saved sign-in status without opening a browser or calling Google.

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
accountNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • addedInput schema / properties / account
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Account"
      +}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: the check is purely local, spawns no browser, and makes no Google API calls, which tells the agent this is cheap and safe to call speculatively. It omits any note about what a failure result looks like, though an 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, no filler, with the scoping constraint front-loaded so the agent learns the local/offline nature immediately. Every clause carries information.

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

Completeness3/5

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

The output schema means return values need not be described, and annotations cover safety, so the description is close to sufficient. The remaining hole is the unexplained account parameter, which leaves an agent guessing whether to pass it when checking a specific saved login.

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

Parameters2/5

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

The single optional parameter "account" has 0% schema description coverage and is never mentioned in the description, so its meaning (which account's saved sign-in is checked, and what happens when omitted) is entirely undocumented. With a non-zero parameter count the 0-param baseline of 4 does not apply.

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?

"Check local configuration and saved sign-in status" gives a specific verb and two concrete resources, and the clause "without opening a browser or calling Google" separates it from live-check siblings such as connection_status. It stops short of naming that sibling, so the differentiation is inferred rather than stated.

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?

The phrase "without opening a browser or calling Google" implies the use case (fast offline diagnostic) but never states when to prefer this over connection_status or list_sites. The agent must infer the routing decision from the negative constraints.

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