Skip to main content
Glama
mcp-google-gsc

mcp-google-gsc

by mharnett

gsc_get_client_context

Retrieves the current Google Search Console client context and health status for your working directory, confirming which Search Console property you are about to query.

Instructions

Get the current GSC client context and health status based on working directory. Call this first to confirm which Search Console property you're working with.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "working_directory": "<working_directory>"
    },
    "name": "gsc_get_client_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
working_directoryYesThe current working directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

A3.8/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. It discloses that output is derived from the working directory and includes a health status, which implies a read-only diagnostic, but it does not say what the context contains, what happens when the directory is unconfigured, or how failures surface.

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 tight sentences with the action first and the routing instruction second. Nothing is redundant or buried.

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 read-only bootstrap tool with no output schema, the description covers purpose, ordering, and the driver of the result. The missing piece is a hint at what the returned context/health actually looks like.

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% for the single working_directory parameter, so the schema already documents it. The description adds only the implication that this directory determines the resolved property, which is marginally useful but not compensation for anything missing.

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 specific verb (Get) and resource (GSC client context and health status) plus a scoping qualifier (based on working directory). It is clearly distinct from gsc_search_analytics or gsc_inspection by virtue of being a context/bootstrap call, though it never names a sibling explicitly.

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

Usage Guidelines4/5

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

"Call this first to confirm which Search Console property you're working with" gives an explicit ordering directive and the reason for it, which is strong usage guidance. It stops short of naming alternatives or stating when-not to call it, so it is not a 5.

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