Skip to main content
Glama
flin-ga4-mcp

flin-ga4-mcp

by flin-agency

health_check

Read-onlyIdempotent

Verifies local configuration and saved login state without network access, token refresh, or browser login.

Instructions

Check local config and saved login state; no network, refresh, or browser login.

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. First observedv0.2.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/closed-world, so the bar is lower, but the description still adds meaningful context: it will not make network calls, refresh tokens, or trigger a browser login. That prevents a common wrong expectation that a health_check validates live credentials.

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?

A single sentence, front-loaded with what is checked and followed immediately by the negative scope. Every clause earns its place; nothing to cut.

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?

Output schema exists so return values need not be explained, and annotations cover the safety profile. The remaining gap is the unaddressed 'account' parameter, which leaves the agent guessing about a visible input.

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?

Schema description coverage is 0% for the single optional 'account' parameter, and the description never mentions it — not what an account value selects, nor what happens when it is null. With the schema silent, the description needed to compensate and does not.

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?

States a concrete verb+resource: check local config and saved login state. It also scopes itself negatively (no network, no refresh, no browser login), which separates it from the account/property tools that hit the API. Not fully sibling-differentiated by name, but the clarification of scope does real work.

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?

Usage is implied rather than stated: use it when you want to verify local state without an API round-trip. It never explicitly says 'use this before running reports' or names an alternative such as a live connection test, so the agent must infer the when/why.

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