Skip to main content
Glama

Google_search_console

by io.github.pipeworx-io

Scan Dependency

scan_dependency
Read-onlyIdempotent

Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesnpm package name. Scoped packages (e.g. "@types/node") are accepted.
versionNoSpecific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted.

TDQS

A4.8/5.0
Behavior5/5

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

Description discloses important behavioral traits beyond annotations: partial failures degrade gracefully, bundlephobia first measurement can take 5-30s, and the 'sources_failed' list will indicate timeouts. Annotations already declare readOnly and idempotent, so description adds context on latency and partial success.

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 description is a single paragraph that front-loads the purpose and then adds usage, return details, limitations, and behavior. It is informative but not excessively long; each sentence adds value. Minor redundancy could be trimmed, but overall well-structured.

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 no output schema, the description fully explains the return value structure: summary block fields, per-advisory details, links, and alternative versions. It also covers edge cases like scoped packages, partial failures, and ecosystem limitation. Everything needed for an agent to understand the tool is present.

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?

Schema coverage is 100% with descriptions for both parameters. Description adds meaningful context: scoped packages are accepted for the 'package' parameter, and 'version' defaults to latest when omitted. This goes slightly beyond the schema alone.

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's purpose as a composite check for npm packages, combining deps.dev and bundlephobia data. It specifies the exact verb 'check' and resource 'npm package', and distinguishes from siblings by noting it's NPM-only in v1.

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

Usage Guidelines5/5

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

Explicitly says when to use: for questions like 'is X safe/popular/small' or 'what does adding lodash cost me'. Also gives a clear exclusion: for other ecosystems, use deps.dev:version directly. This provides clear guidance on when and when not to use.

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

All Google_search_console toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

The set has several overlapping clusters: ask_pipeworx and ask_pipeworx_beta are explicitly identical, multiple polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) occupy the same prediction-market space, and ai_visibility_check/scan_competitor_ai_presence are near-duplicates. A few tools (memory triad, gsc_* calls) are crisp, but the boundaries between the meta-research tools (ask_pipeworx, deep_research, discover_tools, validate_claim) are not obvious enough to prevent misselection.

Naming Consistency2/5

Naming is a mixed bag: some tools follow snake_case verb_noun (gsc_list_sites, resolve_entity, search_within), others are lowercased concatenations (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and several are bare nouns or adjectives (recent_alerts, forget, recall, process). There is no consistent verb style or separator convention across the set.

Tool Count1/5

35 tools is already heavy, but the bigger problem is that only 4 of them (gsc_list_sites, gsc_list_sitemaps, gsc_inspect_url, gsc_search_analytics) relate to the server's stated Google Search Console purpose. The remaining 31 are a sprawling Pipeworx data/prediction-market/memory toolkit, making the count wildly disproportionate to the apparent scope.

Completeness1/5

For a Google Search Console server, the surface is severely incomplete: it can list sites/sitemaps, inspect URLs, and query analytics, but lacks sitemap submission, property add/remove, URL removal/access control, and other core GSC operations. Conversely, the 31 off-domain tools make the domain itself incoherent — an agent cannot tell what this server is actually for.

Resources