Skip to main content
Glama

Arcgis Chapelhill

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 declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context: it returns category-bucketed examples from the live catalog, includes the exact tool+argument shape, and supports a topic parameter to filter results. This goes beyond the annotations without contradicting them.

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 longer than average but front-loaded with user-facing example questions that immediately convey intent. Every clause earns its place—purpose, return structure, and usage are covered. It could be trimmed slightly, but the structure is effective for an onboarding tool.

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?

Even without an output schema, the description fully explains what to expect: category-bucketed example questions, exact tool+argument shape, and the ability to focus by topic. It also covers when to use it and mentions the meta-tools it helps introduce. For a read-only onboarding tool with one optional parameter, this is complete.

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 coverage is 100%, and the description essentially reiterates the schema ('pass `topic` to focus', 'no arguments for the full spread'). It adds minor context by giving example values like 'finance', 'pharma', and 'betting', but does not introduce new semantics beyond the schema's inline 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 this is 'the onboarding entry point' and 'Returns category-bucketed example questions' with 'exact tool + argument shape'. It differentiates itself from siblings like ask_pipeworx and discover_tools by explicitly positioning itself as the tool to use when the agent doesn't yet know what Pipeworx can do.

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?

Explicitly says 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools'. Also provides concrete calling patterns: no arguments for the full spread, or pass a topic to focus. This is strong when-vs-alternative guidance.

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

All Arcgis Chapelhill 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.8/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently literally identical, and the polymarket_* family (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread, polymarket_edge_tracker) all orbit the same prediction-market opportunity space. The descriptions are detailed and do help, but the sheer number of near-synonymous entry points makes misselection likely.

Naming Consistency4/5

The vast majority of tools follow a consistent snake_case, verb-first pattern: ask_pipeworx, compare_entities, query_layer, resolve_entity, search_datasets, validate_claim. Minor deviations exist — the polymarket_* tools are noun-phrase style and a few names like entity_profile, layer_info, and ai_visibility_check are noun-led — but the overall style is uniform enough to be predictable.

Tool Count2/5

34 tools is already in the overstuffed range, but the bigger problem is that only 3 of them (search_datasets, layer_info, query_layer) relate to the server's stated ArcGIS/Chapel Hill identity. The other 31 tools appear to be an unrelated Pipeworx data-research, prediction-market, memory, and subscription bundle merged into this server, making the count grossly disproportionate to the apparent purpose.

Completeness2/5

The three GIS tools form a usable read-only search → schema → query workflow, so the ArcGIS domain is not completely absent. However, as a whole the server has no coherent domain to be complete for, and the ArcGIS side lacks broader capabilities like layer enumeration, spatial filters/statistics, or any write/edit operations. For a server named Arcgis Chapelhill, having 31 out-of-scope tools constitutes a major completeness failure.

Resources