Skip to main content
Glama

Woocommerce

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. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare read-only, idempotent, etc. Description adds fallback behavior (GDELT→GNews), API sunset note, and structured return format, going beyond 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?

Well-structured with front-loaded examples, but slightly dense; every sentence adds value, though could be trimmed slightly.

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?

Despite no output schema, description explains output structure (changes grouped by source, total_changes, citation URIs). Covers fallback and limitations.

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 already covers 100% with descriptions; description elaborates on 'since' with relative formats and 'value' with ticker/CIK examples, adding value.

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?

Description clearly states the tool provides a 'change feed for a company' from multiple sources (SEC, GDELT/GNews, USPTO) and contrasts with sibling 'entity_profile'.

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 gives example queries and when to use 'entity_profile' instead. Provides guidance on 'since' parameter usage with relative shorthand.

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

All Woocommerce 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 five WooCommerce tools are clearly distinct, but the remaining 31 Pipeworx tools contain several overlapping query/research entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim) that an agent would struggle to tell apart without deep inspection. The context of the server also misleads: an agent expecting WooCommerce tools must navigate a much larger unrelated research toolkit.

Naming Consistency2/5

The woo_* tools follow a clean verb_noun pattern, but the bulk of the set uses wildly mixed conventions: bare verbs (forget, recall, subscribe), noun phrases (entity_profile, recent_changes), generic names (ask_pipeworx, discover_tools), and vendor-prefixed variants (pipeworx_trending, polymarket_edges). There is no single naming system across the server.

Tool Count2/5

36 tools is far too many for a server whose apparent purpose is WooCommerce store access; only 5 tools actually relate to WooCommerce. The remaining 31 are an unrelated general-purpose data research suite, making the toolkit feel bloated and mis-scoped.

Completeness1/5

The WooCommerce surface is severely incomplete: it only supports read operations (get/list for products, orders, customers). There are no create, update, delete, refund, or other write operations, so an agent cannot actually manage a store. The unrelated Pipeworx tools do not fill these gaps.

Resources