Skip to main content
Glama

Google_search_console

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and no destructive hint. The description adds behavioral context: fans out to three sources, GDELT preferred with GNews fallback, USPTO soft-fail until reactivated. No contradiction with annotations.

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 dense paragraph that front-loads the purpose with example queries. It covers all key aspects but could be better structured for readability (e.g., bullet points). Still highly informative without waste.

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?

Despite no output schema, the description explains return format: 'structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs'. It covers purpose, parameters, sources, fallbacks, and sibling differentiation, making it complete for the tool's complexity.

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. The description adds value by explaining 'since' accepts ISO date or relative shorthand with examples ('7d', '30d', '3m', '1y'), clarifying 'value' can be ticker or CIK, and noting 'type' only supports 'company'.

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 it is a change feed for a company, aggregating SEC filings, news, and patents. It provides specific example queries ('what's new with X') and explicitly distinguishes from sibling tool 'entity_profile' for static profiles.

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?

It explains when to use (e.g., 'latest on Y', 'updates on Acme') and when not to ('Use entity_profile instead when you want the static profile'). It details fallback logic (GDELT→GNews) and acknowledges limitations (USPTO soft-fail), providing explicit guidance.

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.8/5.0
Disambiguation3/5

Most tools have distinct purposes within their own clusters, and the GSC tools are clearly separated. However, ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, and the several Polymarket tools (arbitrage, edges, fill_risk, kalshi_spread) can be confused without reading each description closely.

Naming Consistency3/5

Names are broadly snake_case and readable, with some useful prefixes (gsc_, polymarket_, pipeworx_). But conventions are mixed: some are verb_noun (list_subscriptions, resolve_entity), some are noun_compound (bet_research, entity_profile), and some are bare verbs (forget, recall), which prevents a predictable pattern.

Tool Count2/5

35 tools is heavy for any single server, but it is especially problematic given the server is named Google_search_console while only 4 of the 35 tools actually relate to Search Console. The rest form a sprawling Pipeworx/Polymarket research toolkit that would be far more coherent as its own server.

Completeness2/5

Relative to the stated Google Search Console purpose, the set is missing common operations such as submitting/removing sitemaps, requesting indexing, or managing URL inspections. The unrelated Pipeworx tools are extensive in their own domains but do not fill these gaps, leaving the GSC surface incomplete.

Resources