Skip to main content
Glama

Arcgis Detroit

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.arcgisonline.com/arcgis/rest/services/Detroit/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/Detroit/FeatureServer/2",
+    "where": "ZONING = 'R1'"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, and idempotent, so the description adds only that results include rows and geometry and that SQL-like filters are supported. It does not discuss authentication, rate limits, or error behavior, which would be useful beyond the 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 four short, purposeful sentences. It front-loads the core purpose, efficiently summarizes the parameter set, states the return type, and offers a practical usage tip without any fluff.

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?

With 6 parameters and no output schema, the description provides purpose, source context, and a return-type hint ('rows (and geometry)'). It lacks a more precise statement of the result format, but the annotations cover safety, making the description adequate for selection and invocation.

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 schema provides 100% coverage with detailed parameter descriptions, so the baseline is 3. The description's listing of parameters is redundant, and the only added value is the sampling tip for where/out_fields; it does not provide deeper semantics beyond the schema.

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 Service / Map Service layer by URL, identifying a specific verb and resource. It distinguishes from sibling tools like layer_info (metadata) and search_datasets (discovery) by focusing on fetching attribute rows.

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?

It advises that the URL comes from search_datasets, implying a preceding discovery step, and gives a concrete sampling pattern (where='1=1' + out_fields='*'). However, it does not explicitly mention when to avoid this tool (e.g., for spatial queries) or name alternatives, so it lacks exclusions.

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

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