Skip to main content
Glama

Data Cityofchicago

by io.github.pipeworx-io

Ask Pipeworx Beta

ask_pipeworx_beta
Read-onlyIdempotent

Beta version of ask_pipeworx: identical universal router (same 5,798 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results are compared against the stable router to decide what merges. Falls back to nothing — this IS a full working router, just the experimental edge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
questionYesYour question or request in natural language. Accepts query, q, prompt, text, input as aliases.

Schema Changelog

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

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), the description discloses that candidate routing improvements may be live during tests, that none are currently active since 2026-07-26, and that it currently matches ask_pipeworx exactly. This is valuable dynamic behavioral context that annotations alone do not provide.

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?

Four sentences, each earning its place: beta status and identity, current state, usage guidance, and a fallback clarification. The most important distinction (beta, experimental) is front-loaded, and the text is dense without unnecessary filler.

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 single-required-parameter router with full schema coverage and rich annotations, the description fully enables correct invocation. It covers current behavior, relationship to ask_pipeworx, and the experimental context. The response shape is addressed by referencing the same response shape as ask_pipeworx, which is sufficient given the sibling context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with every parameter documented as an alias for 'question', so the schema already carries the full burden. The description adds no new parameter-level meaning beyond referencing that arguments are the same as ask_pipeworx, which is already implied by the schema.

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 states a specific purpose: a beta version of ask_pipeworx that is an identical universal router with the same 5,798 tools, arguments, and response shape, but with candidate routing improvements enabled when under test. It clearly differentiates itself from ask_pipeworx and other siblings by emphasizing its experimental edge and current equivalence to the stable router.

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?

The description explicitly says to use it exactly like ask_pipeworx when you want the newest routing, and that results are compared against the stable router. It names the sibling ask_pipeworx and gives the condition that selects this tool, while also clarifying that it is a full working router, not a fallback.

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

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

C2.9/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve query/research; polymarket_edges, polymarket_arbitrage, bet_research, and polymarket_edge_tracker all analyze prediction markets; entity_profile, compare_entities, and recent_changes overlap on company research. An agent could easily select the wrong one.

Naming Consistency3/5

All names are lowercase snake_case, but the verb-noun convention is inconsistent: some are verb-first (ask_pipeworx, generate_llms_txt, validate_claim), some noun-first (entity_profile, polymarket_edges, recent_changes), and some are bare nouns (query, metadata, datasets). The pattern is readable but not uniform.

Tool Count2/5

34 tools is excessive for the apparent scope, especially given the server name suggests a Chicago city-data focus while the vast majority of tools are generic data-research, prediction-market, and memory utilities. This feels like a kitchen-sink bundle rather than a focused, well-scoped toolset.

Completeness2/5

The tool surface is a disjointed collection covering querying, research, memory, subscriptions, and prediction markets, but it lacks coherent lifecycle coverage for any single domain. For the named 'Cityofchicago' purpose, there is almost no city-specific functionality, and even as a general data tool, obvious gaps remain (e.g., no direct dataset management or update/delete operations).

Resources