Skip to main content
Glama

Data Detroit

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Detroit Query

detroit_query
Read-onlyIdempotent

Query any Detroit ArcGIS layer by service path + layer id. Full ArcGIS query: where, out_fields, order_by, limit. Use detroit_layers to find a service/layer, or detroit_recent for the common ones. Epoch dates are converted to ISO.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerYesLayer id within the service (from detroit_layers), e.g. 39.
limitNoMax rows (default 100, max 2000).
whereNoArcGIS SQL where (default "1=1").
serviceYesArcGIS service path, e.g. "RMS_Crime_Incidents/FeatureServer" (or a short name: crime|service_requests|permits).
order_byNoSort clause, e.g. "incident_occurred_at DESC".
out_fieldsNoComma-separated fields, or "*" (default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "layer": 0,
+    "limit": 50,
+    "service": "crime",
+    "where": "OFFENSE='THEFT/OTHER'"
+  },
+  {
+    "layer": 39,
+    "limit": 100,
+    "order_by": "incident_occurred_at DESC",
+    "service": "RMS_Crime_Incidents/FeatureServer"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark it as read-only, idempotent, and non-destructive. Description adds specific behavioral detail: 'Epoch dates are converted to ISO.' No contradictions, but could mention defaults (like max limit 2000) which are in schema but not in description. Still adds value beyond 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?

Two sentences, no redundancy. First sentence clearly states core function. Second provides essential usage guidance and a specific behavior note. Every sentence earns its place.

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?

For a complex query tool with 6 parameters and no output schema, the description covers the core query verbs, date conversion, and guidance to sibling tools. Could mention result format or pagination hints, but schema covers limits. Overall fairly complete.

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 all 6 parameters with descriptions (100% coverage), so baseline is 3. Description adds context by summarizing the key parameters ('where, out_fields, order_by, limit') and mentions epoch date conversion, which is not in schema. Provides meaningful semantic addition.

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?

Clearly states the tool queries Detroit ArcGIS layers by service path and layer ID, with full ArcGIS query parameters. Distinguishes from sibling tools detroit_layers and detroit_recent by directing users to them for finding layers.

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?

Explicitly recommends using detroit_layers to find service/layer IDs and detroit_recent for common ones. Implicitly indicates when to use this tool (when you need to query data) and when to use alternatives (to discover layers), but lacks explicit 'when not to use' statements.

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

All Data 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