Skip to main content
Glama

Arcgis Chestercounty

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://services.arcgis.com/sharing/rest/content/items/.../FeatureServer/0",
+    "where": "1=1"
+  },
+  {
+    "limit": 100,
+    "out_fields": "PARCEL_ID,ADDRESS,OWNER",
+    "url": "https://services.arcgis.com/sharing/rest/content/items/.../FeatureServer/2",
+    "where": "ZONING = 'Residential'"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive hints. The description adds that it returns 'attribute rows (and geometry)' and provides a concrete sampling technique, giving useful behavioral context beyond the annotations without contradicting them.

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 two sentences, front-loaded with the primary verb and resource, and each clause adds value: target resource, parameter list, return format, and sampling tip. No wasted words.

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?

For a read-only query tool with a fully documented schema and no output schema, the description covers the essential context: source of URL, parameter usage, return type (attributes + geometry), and a quick-start sampling pattern. It is sufficient for an agent to select and invoke the tool correctly.

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?

The input schema has 100% coverage, documenting all 6 parameters with descriptions (e.g., 'SQL where clause', 'Max features (1-2000, default 50)'). The description only adds a usage tip, not new parameter semantics, so it doesn't exceed the baseline of 3.

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 starts with a specific verb ('Query') and resource ('ArcGIS Feature Service / Map Service layer'), clearly indicating the tool's function. It also mentions the origin URL from 'search_datasets', which distinguishes it from sibling tools like 'layer_info' and 'search_within'.

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 notes the URL comes from 'search_datasets', implying a prerequisite workflow, and offers a sampling pattern ('Use where="1=1" + out_fields="*" to sample'). However, it does not explicitly state when to use alternatives or provide exclusions, so it falls 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 Chestercounty 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