Skip to main content
Glama

Data Tours

by io.github.pipeworx-io

What Can I Ask Pipeworx?

suggest_questions
Read-onlyIdempotent

What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass topic (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.

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?

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description adds beyond this by detailing the output structure (categories and example questions) and the effect of the topic parameter.

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: starts with sample queries, then states purpose and output, then usage guidance. Every sentence adds value, though it could be slightly more concise.

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?

Despite lacking an output schema, the description fully explains what the tool returns and how to use it. It covers purpose, parameters, output, and usage context, making it complete for an onboarding tool.

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%, so the baseline is 3. The description adds value by listing possible topic values and explaining that omitting it gives a full spread, enhancing the schema's description.

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's purpose: to return category-bucketed example questions with exact tool+argument shapes, serving as an onboarding entry point. It distinguishes itself from siblings by specifying its use in initial exploration.

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 explicitly advises using this tool first when unsure of Pipeworx's capabilities, and provides guidance on passing a topic for focus. It lacks explicit when-not scenarios but this is acceptable given the clear context.

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

All Data Tours 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

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose. Even closely related tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research are well-differentiated by their use cases and safety guarantees. The multiple polymarket tools each focus on a unique aspect (arbitrage, edge scanning, persistence, fill risk, cross-venue spreads), avoiding ambiguity.

Naming Consistency4/5

All tool names use lowercase with underscores, following a mostly verb_noun or domain_prefix_noun pattern (e.g., ask_pipeworx, entity_profile, resolve_entity). A few names like dataset_info and ai_visibility_check deviate slightly from a strict verb_noun structure, but the overall pattern is predictable and readable.

Tool Count4/5

With 33 tools, the server is on the heavier end of the well-scoped range. However, the count is justified by the breadth of functionality: data queries, prediction markets, entity resolution, memory, monitoring, and more. The tools each serve a specific purpose, and none feel redundant.

Completeness4/5

The tool surface covers a wide range of use cases including data retrieval, comparison, research, monitoring, and memory. Minor gaps exist (e.g., no tool for placing prediction market trades or creating/updating Tours Métropole datasets), but these are likely intentional scope choices. Core workflows are well-supported.

Resources