Skip to main content
Glama

Statbank Md

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations are all false/neutral, so the description carries the burden and does so richly: rate-limited to 5 per identifier per day, free/no quota, returns claim_token, team reads digests daily, roadmap impact. 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 dense and front-loaded, with no filler, but it is relatively long and packed with multiple clauses. Every sentence serves a purpose; it could be slightly more scannable, but it is still efficiently structured.

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?

With no output schema and a nested parameter object, the description fully compensates: it states what the claim_token return means, how to read the reply later, rate limits, scope limitations, and the type of message expected. An agent has enough to invoke and follow up correctly.

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 meaningful usage semantics: how to pass claim_token later, to avoid pasting end-user prompts, and to describe issues in terms of Pipeworx tools/packs. This goes well beyond the schema's baseline.

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 opens with a specific verb+resource ('Tell the Pipeworx team something is broken, missing, or needs to exist') and enumerates exact use cases (bug, feature/data_gap, praise). It clearly distinguishes itself from sibling tools by being the dedicated feedback/reporting channel.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance for each feedback type and an explicit exclusion: if the tool came from a different MCP server, report it elsewhere. Also explains the claim_token flow for follow-ups, making alternatives and prerequisites clear.

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

All Statbank Md 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

Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical in scope, and the prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) share similar functions. While some tools are distinct, the boundaries between many are unclear.

Naming Consistency2/5

Names mix product-like identifiers (ask_pipeworx, deep_research), descriptive nouns (entity_profile, subjects), and inconsistent verb forms (query_table, resolve_entity, scan_competitor_ai_presence). No consistent verb_noun pattern is maintained across the set.

Tool Count2/5

With 34 tools, the server is overpopulated relative to its apparent purpose. The name 'Statbank Md' suggests a narrow statistical service, but only 3 tools are Statbank-specific; the rest form a sprawling general-purpose data toolkit. The count is far beyond what the core function needs.

Completeness3/5

For the Statbank subset, the surface is complete (browse subjects, get metadata, query data). As a general data research suite, it covers many domains (SEC, FDA, economics, prediction markets) but lacks execution/trading tools for prediction markets and has no bulk data export or analytics beyond excerpts. Notable gaps exist but many core workflows are covered.

Resources