Skip to main content
Glama

Data Oakland

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Oakland Open Data dataset by resource_id (e.g. "ym6k-rx7a"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNoSoQL $group column(s).
limitNoMax rows (default Socrata 1000).
orderNoSoQL $order, e.g. "date DESC".
whereNoSoQL $where filter, e.g. "year >= 2020 AND status = 'Active'".
offsetNoPagination offset.
selectNoSoQL $select, e.g. "name, count(*) AS n".
resource_idYesDataset id, e.g. "ym6k-rx7a" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "ym6k-rx7a",
-    "where": "year >= 2020"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "ym6k-rx7a"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "ym6k-rx7a",
+    "where": "year >= 2020"
+  }
+]
  3. 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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds meaningful behavioral context beyond annotations: it states that the tool returns matching rows as JSON and that SoQL clauses must not include the leading $, which is a non-obvious execution detail.

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 with zero filler: the first establishes the verb, resource, and example; the second lists the supported clause parameters and the return format. Every word carries information, and the key usage detail (no leading $) is 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?

Given seven parameters but no output schema, the description covers the essential behavior: the query mechanism, clause names, limit/offset usage, and the JSON return type. It does not explain pagination edge cases or error behavior, but with a fully-documented schema and strong annotations, the agent has enough to invoke the tool correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra semantic value by noting that where/select/group/order are SoQL clauses and that they should be provided without the leading $, which the schema does not mention. The resource_id example reinforces the parameter's purpose without needing to open the schema.

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 opens with a specific verb and resource: "Run a Socrata SoQL query against a Oakland Open Data dataset by resource_id". It gives a concrete example ID and clearly separates this tool from siblings like datasets or metadata by focusing on row-level querying with SoQL clauses.

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

Usage Guidelines3/5

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

It explains how to use the tool (which SoQL clauses to pass, that $ should be omitted, and that limit/offset are supported), but it does not explicitly state when to prefer this tool over alternatives or mention exclusions. The context is clear enough for someone who already knows which dataset they want, but no alternative routing is given.

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

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