Skip to main content
Glama

Arcgis Eagan

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.6/5.0
Behavior5/5

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

Goes well beyond the minimal annotations (all false). Discloses the claim_token flow for later status checks, daily digest processing, rate limits (5/day/identifier), and that it's free and doesn't count against tool-call quota. Also warns that reporting other servers' issues will only delay resolution. 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 long, but the tool's behavior is complex (multiple feedback types, claim tokens, exclusions, rate limits). It's front-loaded with purpose and usage. Minor redundancy in the 'ONLY for Pipeworx tools' point repeated later, but no wasted sentences.

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?

No output schema exists, so the description must explain return values — it does (claim_token, later status). It also covers rate limits, quota impact, and the team's workflow. For a feedback tool with nested context objects, all essential operational details are present.

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%, so the schema carries the parameter documentation. The description adds a usage pattern for claim_token (pass it back later to read status), but doesn't substantially expand on the schema's parameter descriptions. Baseline 3 is appropriate.

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: telling the Pipeworx team about broken, missing, or desired functionality. It uses specific verbs ('tell', 'broken', 'missing', 'needs to exist') and distinguishes it from siblings like ask_pipeworx or discover_tools by focusing on feedback about Pipeworx tools/packs.

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?

Explicit when-to-use guidance: bugs, feature/data_gap, praise. Also explicit when-not-to-use: tools from other MCP servers. Includes a decision heuristic for uncertain cases ('Not sure? Pipeworx tool names are the ones this connection lists'). This is modeled after the high-quality TDQS examples.

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

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

Several tool groups overlap heavily: the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) differ mainly in guarantees, and six Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) all target the same trading-concept space with fuzzy boundaries. While ArcGIS, memory, and subscription tools are distinct, an agent will frequently struggle to pick the right research or analysis tool.

Naming Consistency2/5

All names are snake_case, but the structural pattern is inconsistent. Some are verb-first (query_layer, search_datasets, validate_claim), others are noun-first or domain-prefixed (entity_profile, layer_info, polymarket_edges, recent_alerts, pipeworx_feedback). There is no predictable verb_noun convention across the set, making it hard to guess a tool's name from its function.

Tool Count2/5

At 34 tools, the set is well above the typical focused-server range, and the server name 'Arcgis Eagan' suggests a narrow GIS purpose while only 3–4 tools are actually ArcGIS-related. The remaining ~30 tools form a broad, unrelated utility collection (Pipeworx data, memory, subscriptions, trending, npm scanning), making the count feel bloated and unfocused.

Completeness2/5

For the primary ArcGIS domain, only search, layer inspection, and querying are supported — there are no create, update, delete, or editing tools, leaving obvious lifecycle gaps. Meanwhile, the Pipeworx side is over-stocked with redundant analysis tools, and the overall mix lacks a coherent coverage story for any single stated purpose.

Resources