Skip to main content
Glama

Arcgis Mobile

by io.github.pipeworx-io
OverviewAdmin

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://gis.cityofmobile.org/arcgis/rest/services/PublicData/Parcels/FeatureServer/0",
+    "where": "1=1"
+  },
+  {
+    "limit": 100,
+    "order_by": "ACRES DESC",
+    "out_fields": "PARCEL_ID,ZONING_CLASS,ACRES",
+    "url": "https://gis.cityofmobile.org/arcgis/rest/services/PublicData/Zoning/FeatureServer/0",
+    "where": "ZONING_CLASS = 'RESIDENTIAL'"
+  }
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows this is a safe read operation. The description adds the return type (attribute rows and geometry) and a usage tip, but does not disclose additional behavioral traits like error cases or rate limits. It is consistent 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the primary purpose. It efficiently lists the key parameters and includes a practical tip without redundancy. Every sentence contributes value.

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?

No output schema, but the description communicates that the tool returns attribute rows and geometry, which is adequate. All parameters are already in the schema. The reference to search_datasets provides workflow context. Minor gaps like explicit pagination behavior are covered by the schema.

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 each parameter described and defaults provided. The description's parameter overview (SQL-like where, comma-separated out_fields, etc.) does not add new semantics beyond the schema. The sampling tip is already implied by schema defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Query) and the resource (ArcGIS Feature Service / Map Service layer), and it connects the tool to search_datasets. However, it does not explicitly differentiate from sibling tools like layer_info, though the query context implies data retrieval rather than metadata.

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?

The description provides clear context for use (layers obtained from search_datasets) and gives a practical sampling tip (where="1=1" + out_fields="*"). It does not mention when to use alternatives or exclusions, but the context is sufficient.

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

All Arcgis Mobile 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.

Resources