Data Cityofchicago

Datasets

datasets

Read-onlyIdempotent

Search dataset catalogue.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "crime"
    },
    "name": "datasets"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`offset`	No

Output Schema

Name	Required	Description
`limit`	No	Result limit applied
`offset`	No	Result offset applied
`results`	No	Array of dataset results

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "crime"
+  },
+  {
+    "limit": 10,
+    "offset": 0,
+    "query": "building permits"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results from Socrata catalog API",
+  "properties": {
+    "limit": {
+      "description": "Result limit applied",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Result offset applied",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of dataset results",
+      "items": {
+        "description": "Dataset metadata",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds no behavioral context beyond the implied 'search', such as pagination behavior or result format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely minimal (3 words). While concise, it lacks sufficient detail, making it under-specified rather than appropriately compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 3 undocumented parameters and no explanation of the dataset catalogue's scope or result structure, the description is inadequate for effective tool use, even though an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

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

Schema description coverage is 0%, meaning the schema provides no parameter descriptions. The description 'Search dataset catalogue' offers no clarification on the 'query', 'limit', or 'offset' parameters, leaving the agent without guidance on how to use them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search dataset catalogue' clearly states the tool's verb and resource. However, it does not differentiate from sibling search tools like 'search_within' or 'deep_research', which may also search catalogues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives such as 'search_within' or 'query'. The description does not specify when not to use it or provide examples of appropriate use cases.

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

All Data Cityofchicago tools Inspect

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.