Skip to main content
Glama
Sign In
@lomi./gsc-mcp

@lomi./gsc-mcp

by lomiafrica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search Console capabilities

gsc_capabilities
Read-onlyIdempotent

Retrieve current authentication mode, scopes, limits, and disclosure notes for this Google Search Console server.

Instructions

Return active auth mode, scopes, limits, and disclosure notes for this server.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds beyond by stating the specific output contents (auth mode, scopes, limits, disclosure notes), providing behavioral context not captured by annotations.

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?

The description is a single, concise sentence that front-loads the key action and outputs. Every word is meaningful, with no redundant information.

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

Completeness5/5

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

Given the tool has no parameters, annotations are clear, and the description fully explains the output (auth mode, scopes, limits, disclosure notes), it is complete for its simplicity. No output schema is needed.

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?

There are no parameters, so schema coverage is 100% by default. The description compensates by clearly stating what the tool returns, which adds meaning beyond the empty schema.

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

Purpose5/5

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

The description clearly states the tool returns specific information: active auth mode, scopes, limits, and disclosure notes. It uses specific verbs and resources, and distinguishes from sibling tools that handle search analytics or other functions.

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 description implicitly indicates when to use the tool (when you need server capabilities), but provides no explicit guidance on when not to use or alternatives. Given its simplicity and zero parameters, this is adequate.

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

Deploy Server

Other Tools