Skip to main content
Glama

Arcgis Cupertino

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Datasets

search_datasets
Read-onlyIdempotent

Search City of Cupertino GIS open geospatial datasets (parcels, zoning, public works & city services) 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 (City of Cupertino GIS).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "parcels"
+  },
+  {
+    "limit": 10,
+    "query": "zoning public works"
+  }
+]
  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 readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds that the tool returns dataset metadata including url, but does not disclose additional behavioral traits like rate limits, pagination, or search matching behavior. With strong annotation coverage, this is adequate but not rich.

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 core purpose, lists return fields compactly, and includes a practical instruction on using the result. No wasted words.

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?

Given no output schema, the description compensates by listing return fields (name, summary, record_count, owner/org, url) and the downstream workflow. The schema covers parameter details. Missing are search behavior nuances like case sensitivity or partial matching, but overall the description is sufficient for an agent to select and invoke the tool.

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 fully covers all three parameters (limit, query, org_id) with descriptions, giving 100% coverage. The description adds minimal extra meaning by mentioning 'by keyword' which maps to query, but does not elaborate on limit or org_id beyond the schema. Baseline 3 is appropriate.

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 City of Cupertino GIS open geospatial datasets by keyword, with a specific resource (parcels, zoning, public works) and a specific action (search). It distinguishes itself from siblings by explicitly mentioning that the returned URL should be passed to query_layer / layer_info, which are separate 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 implies when to use this tool: when you need to discover datasets by keyword before accessing data. It points to alternatives (query_layer / layer_info) as the next step, providing a clear workflow. However, it does not explicitly state when not to use this tool or mention alternative search tools.

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

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