Skip to main content
Glama

Chile Procurement

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

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

Annotations provide basic hints (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). The description adds significant behavioral context: returns new subscription id, requires OAuth, delivery constraints (10 SMS/day, webhook auto-disable, signing secret one-time return), and type-specific examples. 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 fairly long but well-structured with clear sections (requirements, supported types, delivery channels). It front-loads the core purpose and uses bullet-like formatting. While slightly verbose, every sentence adds necessary detail given the tool's complexity.

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?

For a tool with 3 parameters (type, params, delivery), nested objects, no output schema, and complex conditional logic, the description covers all essential aspects: requirements, type-specific param structures, delivery options with constraints, and behavior. It is fully self-contained.

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 substantial meaning: explains each type-specific params with real-world examples (e.g., sec_8k with items codes, polymarket_edge with topics), delivery channel constraints and verification requirements. This goes well beyond the schema's basic descriptions.

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' with specific verb ('Create') and resource ('subscription'). It distinguishes from siblings like list_subscriptions, unsubscribe, recent_alerts by focusing on creation.

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 clarifies when to use by detailing supported subscription types and delivery channels, and mentions prerequisites (Pipeworx OAuth account). It does not explicitly state when not to use, but context is sufficient.

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

All Chile Procurement 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

Many tools are distinct, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) heavily overlaps—the beta is explicitly identical to the stable version. The two Chile-specific tools are clear, but the presence of numerous unrelated data tools creates confusion about which tool serves the server's purported purpose.

Naming Consistency2/5

Naming is inconsistent: some tools follow verb_noun snake_case (chile_get_tender, chile_search_tenders), others use plain verbs (ask_pipeworx) or noun_verb patterns (polymarket_arbitrage, entity_profile). Mixed conventions and varying levels of specificity make the set feel uncoordinated.

Tool Count2/5

33 tools is excessive for a server named 'Chile Procurement'—only two tools relate to Chile procurement, while the rest are generic Pipeworx data utilities. The count is not scoped to the server's stated purpose; it appears to be a bundled general-purpose toolkit rather than a focused procurement interface.

Completeness2/5

For Chile procurement, only search and get-detail are provided; there is no ability to list all historical tenders, filter by category or amount, or track bidding. The read-only surface covers basic retrieval but lacks common procurement workflows. The broader data tools are complete individually but irrelevant to the server's domain.

Resources