Skip to main content
Glama
GSC Opportunity MCP

GSC Opportunity MCP

by caomicc

health_check

Verifies authentication and configuration status without hanging on expired tokens, keeping headless workflows running.

Instructions

Auth + config status. Never hangs on expired tokens (headless-safe).

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

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: it 'never hangs on expired tokens (headless-safe)', telling an agent it is safe to call without risk of blocking. However, it never states that the tool is read-only/non-mutating, whether it requires credentials to run, or what kind of status it returns, so the behavioral picture is only partly covered.

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 short sentences with no filler, and the safety guarantee is front-loaded after the purpose. The telegraphic style ('Auth + config status') is slightly clipped but still unambiguous in context.

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 zero-parameter, read-style check with an output schema already documenting return values, the description supplies what is needed: what the tool inspects and the key call-safety guarantee. Stating explicitly that it is non-mutating would make it fully complete.

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 and the schema coverage is 100%, so there is nothing for the description to disambiguate. The baseline of 4 applies to a no-argument tool.

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

Purpose3/5

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

The phrase 'Auth + config status' identifies the subject matter (authentication and configuration state) but is a terse noun fragment rather than a verb+resource statement. Combined with the name health_check an agent can infer it returns a status report, but the description itself never says it returns or reports anything, and offers no distinction from the sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this tool, when not to, or what alternatives exist. The 'headless-safe' note implies a suitable context (automated/headless runs) but does not state it as a usage rule or exclusion.

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