Skip to main content
Glama

Simap

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.

Schema Changelog

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

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description details delivery channels, sms cap, webhook auto-disable, and the returned subscription id. It does not clarify idempotency behavior for duplicate subscriptions, but overall provides good behavioral context.

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 moderately long but well-structured with bullet-like lists and front-loaded purpose. It could be slightly more concise, but effectively conveys necessary details without excessive verbosity.

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?

Given the tool's complexity (multiple types, delivery channels, OAuth requirement), the description covers nearly all essential aspects. Minor gaps include rate limits on subscription creation and idempotency behavior. No output schema, but the return value is mentioned.

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?

With 100% schema coverage, baseline is 3, but the description adds rich examples and details for each type (e.g., sec_8k items, polymarket_edge topic) and delivery options (webhook signing, sms verification), significantly enhancing param understanding.

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 explicitly states 'Create a proactive monitoring subscription to a live-data event stream' and specifies it returns the new subscription id. It clearly distinguishes from sibling tools like list_subscriptions and unsubscribe.

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 clear context for when to use the tool, including the requirement for a Pipeworx OAuth account and that the feed is always accessible via recent_alerts. However, it could more explicitly state when not to use subscribe (e.g., if only pulling existing alerts).

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

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

There are several tools with overlapping query responsibilities: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-variants of the same router, and bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunity discovery. An agent must read the long descriptions carefully to distinguish them, and some variants are behaviorally identical today.

Naming Consistency3/5

All names are readable snake_case, but the verb_noun convention is not consistently applied: some are clean verb phrases like validate_claim and discover_tools, while others are noun phrases like entity_profile, recent_alerts, or simap_project. The prefixed groups (polymarket_*, pipeworx_*) help, but the overall naming style is mixed.

Tool Count2/5

34 tools is above the heavy range, and the set is inflated by redundant router variants, five overlapping Polymarket tools, and loosely related utilities like generate_llms_txt and scan_dependency. The server is named Simap but only three tools relate to Swiss procurement, making the scope feel bloated and misaligned.

Completeness4/5

For an information-retrieval-style server, the core workflows are well covered: discovery, routing, grounded answers, entity resolution, profiles, comparisons, fact-checking, subscriptions, and memory. The main gaps are minor, such as updating a subscription in place or deeper native Simap-specific actions, and those can be worked around.

Resources