Skip to main content
Glama
Sign In

Seonix

by io.github.pahaa97
OverviewDiscussionsAdmin

Indexing coverage

gsc_coverage
Read-onlyIdempotent

Indexing coverage Seonix collected from Search Console: indexed / not indexed / unknown counts, sitemap status, and the pages that are not indexed with Google's verdict.

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_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id or slug. Optional when the account has one project or the connector URL names it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and a closed-world scope, so the safety profile is covered. The description adds useful context that the data is collected from Search Console and what coverage categories are returned, but it does not disclose freshness, pagination, or response-shape details.

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?

The definition is a single front-loaded sentence that packs in the source, the metrics, and the non-indexed-page detail without obvious repetition. It is appropriately sized, though the phrasing 'Indexing coverage Seonix collected from Search Console' is slightly awkward and could be clearer.

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 low-complexity, read-only analytics tool with one optional parameter, the description is mostly complete: it explains what is returned and where it comes from. It does not mention how the optional project_id affects scope or whether coverage is a current snapshot, but the rich annotations and full schema coverage keep the gap small.

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 description coverage is 100%, and the only parameter is an optional project_id that is already documented in the schema. The description does not add meaning beyond the schema, so the baseline score of 3 is appropriate.

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?

The description names a specific resource, Search Console indexing coverage, and lists the exact data returned: indexed/not indexed/unknown counts, sitemap status, and non-indexed pages with Google's verdict. It is clear what the tool provides, though it does not explicitly contrast itself with nearby GSC siblings such as gsc_status or gsc_opportunities.

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 explicit when-to-use guidance, no conditions for selecting it over sibling tools, and no exclusions. The agent must infer from the name and data categories that this is the indexing coverage report rather than another GSC analytics tool.

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

All Seonix toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources