Skip to main content
Glama

Arcgis Kansas

by io.github.pipeworx-io

Search Datasets

search_datasets
Read-onlyIdempotent

Search Kansas State GIS open geospatial datasets (parcels, zoning, transport & statewide GIS layers) by keyword. Returns each dataset's name, summary, record_count, owner/org, and its Feature Service url — pass that url to query_layer / layer_info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax datasets (1-50, default 20).
queryNoKeyword(s), e.g. "parcels", "crime", "flood zones".
org_idNoOptional ArcGIS orgId to override the default (Kansas State GIS).

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: +[
+  {
+    "query": "parcels"
+  },
+  {
+    "limit": 10,
+    "query": "flood zones zoning"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the description's main added value is the specific return fields (name, summary, record_count, owner/org, url) and the type of data (open geospatial datasets). This adds useful context beyond the annotations, though it does not cover rate limits or org_id override 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?

The description is two sentences: the first states the core functionality and scope, the second lists return values and directs the user to downstream tools. No wasted words; information density is high and front-loaded.

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 no output schema, the description compensates by listing the return fields and the downstream use case. It covers the core functionality and integration, but does not address edge cases like org_id override effects or pagination. This is slightly above adequate given the moderate complexity and strong schema coverage.

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%, so the baseline is 3. The description does not add significant parameter-level semantics beyond what the schema already provides, but it reinforces that 'query' is a keyword search and that 'org_id' is an override. This meets the baseline without exceeding it.

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 searches Kansas State GIS open geospatial datasets by keyword, with specific examples of dataset types (parcels, zoning, transport). It distinguishes itself from siblings by detailing the return fields and the workflow of passing the URL to query_layer/layer_info.

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 as the discovery step before query_layer/layer_info, implicitly distinguishing it from those tools. It does not explicitly mention when to use it over other search tools, but the workflow guidance is strong.

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

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

TDQS

A3.5/5.0
Disambiguation1/5

Many tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all route questions; polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker all deal with prediction market edges). The inclusion of memory tools (remember, recall, forget) alongside research tools further blurs boundaries.

Naming Consistency2/5

Naming conventions are mixed: some tools use snake_case (ai_visibility_check), some use underscores with prefixes (ask_pipeworx, polymarket_arbitrage), and others are more generic (query_layer, layer_info). There is no consistent pattern across the set.

Tool Count2/5

With 34 tools, the set is overly large for a geospatial server; most tools are unrelated to ArcGIS Kansas (e.g., prediction market tools, general research tools). Only 3 tools (search_datasets, layer_info, query_layer) are pertinent, making the count excessive and unfocused.

Completeness1/5

The server claims to be an ArcGIS Kansas tool but provides only basic layer querying and dataset search. Missing essential GIS operations such as editing, spatial analysis, or advanced queries, making it severely incomplete for its stated purpose.

Resources