Skip to main content
Glama

Worldbank Poverty

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

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

Annotations provide idempotentHint (true) and openWorldHint (true). The description adds significant behavioral context: OAuth requirement, return of new subscription id, type-specific parameterization, delivery constraints (SMS cap, phone verification, webhook auto-disable). It does not contradict annotations, though idempotency is not explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured paragraph that front-loads the core action and progressively adds details (prerequisites, types, channels). Every sentence serves a purpose; no redundancy. It is information-dense yet easy to parse.

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?

For a tool with 3 parameters and no output schema, the description covers return value (subscription id), prerequisites, all supported types with examples, and delivery options with constraints. It lacks mention of subscription limits or retry behavior, but overall completeness is high.

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 covers all parameters (100% coverage), but the description enriches semantics with concrete examples (e.g., items codes for sec_8k, topic for polymarket_edge) and usage details (webhook signing, SMS verification). This goes well beyond the baseline, making parameters intuitively understandable.

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 purpose: 'Create a proactive monitoring subscription to a live-data event stream.' It specifies the action (create), resource (subscription), and outcome (returns subscription id). The tool's role is distinct from siblings like list_subscriptions and unsubscribe, even though not explicitly compared.

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

Usage Guidelines3/5

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

Usage is implied by the description (e.g., requires OAuth account, types, delivery channels), but there is no explicit guidance on when to use this tool versus alternatives like list_subscriptions or recent_alerts. The context from sibling tools helps, but the description itself lacks direct when-to-use instructions.

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

All Worldbank Poverty 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.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) which all route to the same data sources. Additionally, the server includes unrelated meta-tools (remember/recall/forget, generate_llms_txt, pipeworx_feedback) that have no clear boundaries with the poverty data tools, and betting tools that seem out of place. The core poverty tools (get_poverty, get_poverty_regional, list_reference) are distinct, but the rest creates significant confusion.

Naming Consistency2/5

Tool names are a mix of styles: some use snake_case (get_poverty, list_reference, suggest_questions), some use camelCase (ask_pipeworx, bet_research, scan_competitor_ai_presence), and others are single words (recall, remember, forget, subscribe). The naming pattern is highly inconsistent, making it hard to predict related tool names.

Tool Count2/5

With 34 tools, this server is heavily overloaded for a 'Worldbank Poverty' server. The majority of tools are unrelated to poverty (Polymarket betting, AI marketing, npm package checks, LLM visibility). The core poverty functionality could be served by 3-5 tools, but instead the server includes dozens of extra tools from a generic data platform, making the count inappropriate for the stated domain.

Completeness4/5

For the poverty data domain, the tool surface is actually quite complete: get_poverty for country-level data, get_poverty_regional for aggregations, and list_reference for metadata. The only minor gap is a lack of a tool for comparing poverty across countries directly, but that is easy to work around by calling get_poverty multiple times. The extra meta-tools do not affect poverty data completeness.

Resources