Skip to main content
Glama

Metmuseum

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate idempotentHint=true, openWorldHint=true, destructiveHint=false, readOnlyHint=false. The description adds behavioral traits: requires OAuth, delivery limitations (SMS 10/day cap), webhook auto-disabling after 10 failures, and phone verification requirement. No contradictions.

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 well-structured with line breaks, front-loading the core purpose. It is slightly lengthy but each sentence adds value. Could be more concise, but overall effective.

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 the tool's complexity (3 params, nested objects, no output schema), the description covers authentication, return value, types, delivery channels, limitations (SMS cap, webhook auto-disable), and phone verification. It is complete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning by explaining the params object in detail for each subscription type and providing examples. It also clarifies delivery channel requirements and constraints beyond the schema.

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 creates a proactive monitoring subscription, returns a subscription ID, and distinguishes itself from siblings like list_subscriptions and unsubscribe. The verb 'Create' and resource 'subscription' are explicit.

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

Usage Guidelines4/5

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

It specifies that a Pipeworx OAuth account is required and anonymous/BYO cannot persist subscriptions. It lists supported types, delivery options, and mentions the always-on feed. It does not explicitly state when to avoid using the tool, but the context and sibling tools provide enough guidance.

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

All Metmuseum 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 server mixes two Met-specific tools (get_artwork, search_artworks) with a large set of generic Pipeworx tools (ask_pipeworx, bet_research, etc.), making it unclear which tools actually relate to the Met museum. Agents will struggle to distinguish the domain-specific tools from the general data tools.

Naming Consistency2/5

Tool names follow no consistent pattern: Met-specific tools use get_/search_/list_ prefixes, while Pipeworx tools use diverse patterns (ask_, bet_, compare_, discover_) and some use underscores while others lack verbs. The inconsistency increases cognitive load.

Tool Count3/5

At 29 tools, the count is high but not unreasonable for a combined server. However, only 3 tools are Met-specific, so the count feels inflated by unrelated tools. A more focused Met server would have fewer tools.

Completeness2/5

For a Met museum server, the tool surface is severely limited: only search, get by ID, and list departments. Missing operations like filtering by artist, retrieving related objects, or accessing collection highlights. The domain coverage is incomplete.

Resources