Skip to main content
Glama

Arcgis Puyallup

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 50,
+    "out_fields": "*",
+    "url": "https://gis.puyallupwa.gov/arcgis/rest/services/PublicServices/Parcels/FeatureServer/0",
+    "where": "1=1"
+  },
+  {
+    "limit": 100,
+    "order_by": "ACRES DESC",
+    "out_fields": "PARCEL_ID,ZONE_TYPE,ACRES",
+    "url": "https://gis.puyallupwa.gov/arcgis/rest/services/PublicServices/Zoning/FeatureServer/0",
+    "where": "ZONE_TYPE = 'Residential'"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. The description adds that it returns attribute rows and geometry, plus a sampling pattern. This is meaningful value beyond annotations, though it omits edge cases like max limit behavior.

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?

Two sentences, front-loaded with the action and resource, and zero wasted words. The sampling tip is immediately useful.

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?

With rich annotations, a fully described schema, and the description covering what, how, and a usage tip, this is complete for an AI agent to select and invoke correctly.

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%, so baseline is 3. The description adds a quick synopsis of parameter roles and a concrete usage tip ('where="1=1" + out_fields="*"') that goes beyond the schema. This warrants a 4.

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 opens with a specific verb ('Query'), identifies the resource ('ArcGIS Feature Service / Map Service layer'), and notes the url comes from search_datasets. It clearly distinguishes from siblings like layer_info (metadata) and search_within (spatial query).

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 explicitly ties usage to search_datasets, indicating when to use this tool. It also includes a practical sampling tip. However, it doesn't explicitly mention alternatives or exclusions, so it's just short of a 5.

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

All Arcgis Puyallup toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources