Skip to main content
Glama

Arcgis Albuquerque

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

A5/5.0
Behavior5/5

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

With annotations providing minimal behavioral info (all false), the description compensates richly by disclosing rate limits (5 per identifier per day), cost (free, no quota impact), claim_token behavior for unauthenticated submissions, and how to use the token to read later status. It also reveals that the team reads digests daily and signal affects roadmap—useful for setting expectations.

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?

The description is dense but every sentence earns its place: purpose, use cases, exclusions, content guidance, token workflow, rate limits, and cost. It is front-loaded with the core purpose and well-structured for an AI agent to parse. No fluff or redundancy.

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 having no output schema, the description explains the key return-value behavior (claim_token) and the lifecycle of a feedback report. It covers operational details like rate limits and cost, and areas the agent might need (what is acceptable content). The tool is moderately complex with nested params and optional context, but the description fully equips an agent to invoke it 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%, so baseline is 3, but the description adds substantial value beyond parameter descriptions. It explains the claim_token parameter's usage pattern (pass it back with no other arguments to read status) and elaborates on the type enum semantics. This goes beyond what the schema provides.

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: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It specifies the resource (Pipeworx team) and the scope (issues with Pipeworx tools/packs), distinguishing it from sibling tools like ask_pipeworx which are for using Pipeworx data rather than providing feedback about the service itself.

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?

Offers explicit when-to-use scenarios: bug, feature/data_gap, and praise. Provides a clear when-not-to-use: for tools from other MCP servers, directing users to file with that server instead. Also instructs what to include (describe in terms of Pipeworx tools/packs, not end-user prompts), making usage criteria unambiguous.

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

All Arcgis Albuquerque 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

Several tool clusters overlap heavily: ask_pipeworx and ask_pipeworx_beta are documented as functionally identical right now, and polymarket_arbitrage / polymarket_edges / polymarket_edge_tracker all surface trade opportunities with similar outputs. discover_tools and suggest_questions also cover similar 'what can I do' territory.

Naming Consistency3/5

All names are snake_case and many use verb_noun (query_layer, resolve_entity, generate_llms_txt), but a large minority use noun/adjective phrases (layer_info, recent_changes, polymarket_edges, bet_research) or bare verbs (remember, forget, recall). The pattern is readable but not fully predictable.

Tool Count2/5

34 tools is over the 25-tool threshold and deeply mismatched with the server name: only 3 of them (search_datasets, query_layer, layer_info) relate to ArcGIS Albuquerque. Most of the surface is a general-purpose Pipeworx data platform, making the set bloated and unfocused.

Completeness2/5

The advertised ArcGIS domain has only search-schema-query coverage: there is no way to list all datasets, apply spatial filters, or get service-level metadata. The Pipeworx half is feature-rich, but for the server as titled the tool surface has significant gaps and a large amount of irrelevant functionality.

Resources