Skip to main content
Glama

Data Oregon

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Oregon Open Data dataset by resource_id (e.g. "tckn-sxa6"). 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. "tckn-sxa6" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 50,
-    "resource_id": "tckn-sxa6",
-    "where": "year >= 2020"
-  },
-  {
-    "group": "category",
-    "order": "total DESC",
-    "resource_id": "tckn-sxa6",
-    "select": "category, count(*) AS total"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "tckn-sxa6"
+  },
+  {
+    "limit": 20,
+    "resource_id": "tckn-sxa6",
+    "select": "registry_number"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 50,
+    "resource_id": "tckn-sxa6",
+    "where": "year >= 2020"
+  },
+  {
+    "group": "category",
+    "order": "total DESC",
+    "resource_id": "tckn-sxa6",
+    "select": "category, count(*) AS total"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the bar is lowered. The description adds valuable behavioral detail beyond the annotations: it states that the tool returns matching rows as JSON, which is important since no output schema exists. It also clarifies that SoQL clauses must be provided without the leading '$', which is a meaningful behavioral nuance.

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 concise sentences that front-load the core action, specify the resource type and identifier, list the supported operations, and state the return format. Every sentence earns its place with no filler or repetition of the schema definitions.

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 7-parameter query tool with no output schema, the description covers the essential elements: target system, dataset identification, SoQL clause syntax, pagination options, and return format. It could additionally mention default behavior or error handling, but the schema documents defaults and parameter details, so the description is sufficiently complete for an agent 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 baseline is 3. The description adds cross-parameter meaning by grouping where/select/group/order as SoQL clauses and calling out limit/offset as separate pagination controls. The explicit note that clauses are written without the leading '$' adds practical semantics beyond what each individual schema description states.

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 identifies the tool's purpose: running a Socrata SoQL query against an Oregon Open Data dataset identified by resource_id. It also specifies the operations supported (filtering with where/select/group/order and pagination) and the output type (JSON), which distinguishes it from sibling tools like datasets or metadata that operate at a different level.

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?

The description explains how to construct a query using SoQL clauses and pagination parameters, but it gives no guidance on when to choose this tool over alternatives. It does not mention exclusions, prerequisites, or explicitly name any sibling tool that should be used instead for other dataset operations.

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

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