Skip to main content
Glama

Crystallography

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.6/5.0
Behavior5/5

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

Annotations indicate no read-only, no destruction, idempotent, and open-world. The description adds behavioral details: requires OAuth, returns new subscription ID, delivery channel options, SMS cap, webhook auto-disable after 10 failures, and HMAC signing. 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 somewhat lengthy but well-structured with clear sections for types and delivery. It front-loads the core purpose and return value. Every sentence adds value, though it could be slightly tightened without losing information.

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 complexity of subscription types and delivery channels, the description is complete. It covers auth requirements, all 5 types with example params, three delivery options with limitations and setup details, and mentions the return value (subscription ID). No output schema exists, so the description compensates adequately.

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%, but the description adds significant meaning beyond the schema. It explains each type (e.g., sec_8k with ticker and items), provides usage examples for params, and details delivery channel options (email, SMS, webhook) with limitations and verification steps. The nested object for delivery is thoroughly explained.

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 creates a proactive monitoring subscription to a live-data event stream and returns the subscription ID. It distinguishes itself from sibling tools like unsubscribe and list_subscriptions, and the specific subscription types are detailed.

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?

The description provides explicit context for when to use: setting up persistent subscriptions. It notes prerequisites (Pipeworx OAuth account), and limits (10/day SMS cap). While it doesn't explicitly list alternatives, it implies that anonymous/BYO accounts cannot persist subscriptions, guiding appropriate usage.

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

All Crystallography 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.7/5.0
Disambiguation2/5

There are three overlapping ask_pipeworx variants (stable, beta, grounded) plus a dense cluster of six polymarket trading/arbitrage tools, making misselection likely. Several other tools also blur together around research aggregation and entity lookup (entity_profile, compare_entities, recent_changes, validate_claim).

Naming Consistency3/5

All tool names are lowercase and snake_case, but the pattern is inconsistent: some are verb_noun (get_structure, resolve_entity), some are noun phrases (recent_changes, polymarket_edges), and a few are bare verbs (remember, forget, recall). The ask_pipeworx_beta/ask_pipeworx_grounded suffix pattern is readable but not mirrored across the rest of the set.

Tool Count2/5

34 tools is above the 25+ threshold for a server whose stated purpose is Crystallography, and only 3 of those tools actually serve that domain. The rest belong to Pipeworx data lookup, Polymarket betting, memory, research, subscriptions, and unrelated utilities, so the count feels excessive and the scope is unclear.

Completeness3/5

As a broad data-research toolset, there is decent lifecycle coverage: lookup, research, grounded verification, entity resolution, comparison, subscriptions, feedback, and memory all exist. However, for a server named Crystallography the domain surface is thin (search/get/get CIF only), and there is no general web-search fallback for topics not in the structured catalog.

Resources