Skip to main content
Glama

Arcgis Delawareco

by io.github.pipeworx-io

Search Datasets

search_datasets
Read-onlyIdempotent

Search Delaware County GIS open geospatial datasets (parcels, addresses, zoning & public works) 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 (Delaware County GIS).

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds value beyond these by specifying the exact returned fields (name, summary, record_count, owner/org, url) and the intended downstream action. It does not contradict 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 two sentences, front-loaded with the primary action and scope, followed by the return value and usage. Every word contributes, with no redundancy or irrelevant details.

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?

Given the tool has no output schema, the description fully compensates by enumerating the return fields. It also explains how to chain with sibling tools (query_layer/layer_info) and notes the optional org_id override, making the tool self-contained for an agent.

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 already provides 100% coverage for all three parameters (query, limit, org_id) with clear descriptions. The tool description adds minor context by mentioning the default Delaware County GIS scope and the workflow, but it does not substantially enhance parameter understanding beyond what the schema provides.

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 Delaware County GIS open geospatial datasets by keyword and returns each dataset's metadata. It distinguishes itself from related tools by explicitly mentioning the Feature Service URL is passed to query_layer/layer_info, which are sibling tools.

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 a clear workflow by instructing the agent to pass the returned URL to query_layer/layer_info, implying usage for dataset discovery. However, it does not explicitly state when not to use this tool or contrast it with other search-focused siblings like search_within, so it is slightly incomplete.

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

All Arcgis Delawareco 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
Disambiguation2/5

Many tools have overlapping or redundant purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical in routing, and several polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) all surface trading opportunities with similar outputs. The three ArcGIS tools are distinct but buried among dozens of unrelated data/meta tools, making selection confusing.

Naming Consistency3/5

All names use snake_case, which is consistent, but the verb/noun pattern is inconsistent. Some are verb_noun (query_layer, resolve_entity), some are noun phrases (entity_profile, polymarket_edges, recent_alerts), and some are bare verbs (recall, remember, forget, subscribe). The naming style is readable but not predictably patterned.

Tool Count1/5

34 tools is already high, but the severe issue is that only 3 of them (search_datasets, query_layer, layer_info) relate to the server's stated ArcGIS Delaware County purpose. The other 31 are Pipeworx data, memory, subscription, and prediction-market tools, which is a blatant scope mismatch. The tool count is not appropriate for the advertised server domain.

Completeness1/5

For an ArcGIS Delaware County GIS server, the surface is extremely thin: only search, query, and layer metadata exist. There are no tools for editing features, uploading data, managing layers, or exporting maps. Conversely, the Pipeworx tools form a broad but fragmented domain with many monitoring and meta-tools but no clear end-to-end workflow. The set is severely incomplete for its apparent dual purpose.

Resources