Skip to main content
Glama

Arcgis Roundrock

by io.github.pipeworx-io

Query Layer

query_layer
Read-onlyIdempotent

Query an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like where, comma-separated out_fields, order_by, limit, offset. Returns attribute rows (and geometry). Use where="1=1" + out_fields="*" to sample.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFeature/Map Service layer url ending in /FeatureServer/<n> or /MapServer/<n>.
limitNoMax features (1-2000, default 50).
whereNoSQL where clause, e.g. "STATE = 'CA' AND YEAR >= 2020". Default "1=1".
offsetNoPagination offset.
order_byNoe.g. "POP DESC".
out_fieldsNoComma-separated field names, or "*" for all (default).

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 50,
+    "out_fields": "*",
+    "url": "https://services.arcgisonline.com/arcgis/rest/services/example/FeatureServer/0",
+    "where": "1=1"
+  },
+  {
+    "limit": 100,
+    "order_by": "ADDRESS ASC",
+    "out_fields": "PARCEL_ID,ADDRESS,ZONING",
+    "url": "https://services.arcgisonline.com/arcgis/rest/services/example/FeatureServer/1",
+    "where": "ZONING = 'Commercial'"
+  }
+]
  2. 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, so agent knows it's safe. Description adds value by confirming return of attribute rows and geometry, and mentioning default limit. No contradictions. Adequate beyond annotations.

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?

Very concise: two sentences plus a usage tip. Front-loaded with main action. Every sentence adds value; no fluff. Excellent structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given full schema parameter coverage and safe annotations, the description covers essentials: what it does, key parameters, and return type. Missing details on error handling or response structure (no output schema), but acceptable for a read-only query tool. Could add note on large results or pagination, but fine.

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% with individual parameter descriptions. The description adds SQL-like syntax examples and a practical sampling tip, providing more than the schema alone. Enhances understanding of how to construct queries.

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 queries an ArcGIS Feature/Map Service layer, specifies parameters (where, out_fields, order_by, limit, offset), and mentions returning attribute rows and geometry. It references the sibling 'search_datasets' for context, distinguishing this as a follow-up query tool.

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?

Provides explicit examples and a sampling tip ('where="1=1" + out_fields="*"'). Implicitly indicates post-search usage by referencing 'from search_datasets'. Does not explicitly state when not to use, but siblings provide context. Clear enough for effective use.

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

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

Multiple tools have overlapping purposes, most notably ask_pipeworx and ask_pipeworx_beta which are currently functionally identical. The prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread) also have fuzzy boundaries that could easily mislead an agent. Entity/company tools like entity_profile, recent_changes, compare_entities, and validate_claim further blur the line between profile, change feed, comparison, and verification.

Naming Consistency3/5

Most tools use snake_case and are readable, but the verb/noun pattern is inconsistent: some are verb-first (query_layer, suggest_questions), some are noun-first (entity_profile, layer_info, recent_alerts), and a few are bare verbs (remember, recall, forget). The ArcGIS trio follows its own convention distinct from the Pipeworx family, adding to the mixed feel.

Tool Count2/5

34 tools is well above the reasonable ceiling for a coherent server, and the vast majority have nothing to do with the server's stated ArcGIS Round Rock identity. This looks like multiple domain suites (GIS, Pipeworx data, Polymarket betting, AI visibility, memory, subscriptions) crammed into one endpoint, making the set feel bloated and unfocused.

Completeness3/5

For the Pipeworx data domain, coverage is quite thorough with query, grounded answer, deep research, entity resolution, validation, discovery, and monitoring. However, for the server's stated ArcGIS Round Rock purpose, only three tools exist (discover, query, layer schema) with no export, geometry operations, or metadata browsing beyond basic layer info. The mixed composition leaves obvious gaps relative to the server name while over-supplying unrelated features.

Resources