Sothebys

Many tools overlap in purpose: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research are all question-routers that differ only in routing version, grounding strictness, or fan-out, and entity_profile / recent_changes / company_facts all answer 'company info' at different time scopes. The descriptions are unusually detailed and do draw the boundaries (e.g. explicit 'prefer X over Y' guidance), which keeps an agent from total confusion, but the three-way router split in particular invites misselection.

Everything is snake_case with no camelCase or style clashes, and domain prefixes (sothebys_, polymarket_, kalshi_) are used consistently per family. Minor inconsistency in that some names are verb-first (validate_claim, resolve_entity, generate_llms_txt) while others are noun-first (entity_profile, company_facts, recent_changes, deep_research), but the convention is still readable and predictable.

38 tools is well into heavy territory, and for a server named 'Sothebys' only two tools (sothebys_results_search, sothebys_lot_details) are actually Sotheby's-specific — the other 36 are a generic Pipeworx gateway surface. Several near-duplicate routers and many niche prediction-market tools feel like catalog breadth rather than a scoped set, making the count disproportionate to the apparent purpose.

For the auction domain the surface is search-plus-detail only: you can find past lots and pull a lot's full record, but there is no upstream auction/sale calendar, no artist- or category-level price aggregation, and no analytics on sold-vs-estimate. Read-only coverage of realized results is solid for what exists, but lifecycle and rollup operations agents would want are missing.