Skip to main content
Glama

Arcgis Lakeland

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/lakeland/rest/services/Parcels/FeatureServer/0",
+    "where": "1=1"
+  },
+  {
+    "limit": 100,
+    "order_by": "AREA DESC",
+    "out_fields": "PARCEL_ID,ZONE_TYPE,AREA",
+    "url": "https://services.arcgis.com/lakeland/rest/services/Zoning/MapServer/1",
+    "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 readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value by specifying the return content: 'Returns attribute rows (and geometry)' and provides a sample usage pattern, complementing the annotation-provided safety profile without contradiction.

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 short sentences, front-loaded with the main action, and every sentence contributes: purpose/source, parameters, return type and usage tip. No redundant phrasing or filler.

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 6-parameter query tool with no output schema and good annotations, the description covers essentials: what it queries, how to obtain the URL, key parameters, return type (rows and geometry), and a practical usage pattern. It is complete enough 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description enhances parameter understanding by labeling `where` as 'SQL-like', and the tip 'where="1=1" + out_fields="*"' illustrates a common pattern for sampling all data, adding meaning 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's function with a specific verb and resource: 'Query an ArcGIS Feature Service / Map Service layer by its url'. It also references 'from search_datasets', distinguishing it from sibling tools like search_datasets (for finding datasets) and layer_info (for metadata). The purpose is unambiguous and well-differentiated.

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 usage context by indicating the URL originates from search_datasets, and offers a practical sampling tip: 'Use where="1=1" + out_fields="*" to sample.' It does not explicitly name alternative tools or state when not to use this tool, but the guidance is sufficient for typical use.

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

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