Skip to main content
Glama

Data Santaclara

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Santa Clara County Open Data dataset by resource_id (e.g. "n9u6-aijz"). 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. "n9u6-aijz" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 100,
-    "resource_id": "n9u6-aijz",
-    "where": "year >= 2020"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "n9u6-aijz"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 100,
+    "resource_id": "n9u6-aijz",
+    "where": "year >= 2020"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds the valuable behavioral detail that results are returned as JSON and that SoQL clauses must be written without the leading '$' – a syntax nuance not implied by the annotations. This enriches the behavioral context beyond the structured data.

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?

A single, well-structured sentence that leads with the core action, immediately explains the SoQL clause syntax, and specifies the return format. Every word earns its place – no filler, no redundancy.

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

Completeness5/5

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

For a query tool with 7 parameters fully documented in the schema, the description adds the missing operational context: the SoQL syntax without '$', the default limit mention is in schema, and the JSON return format. Nothing an agent needs to call it correctly is missing; annotations cover safety, and the schema covers parameters.

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?

Schema description coverage is 100%, so the schema already documents every parameter (where, select, group, order, limit, offset, resource_id). The description adds the crucial 'without the leading $' rule and a concrete example, which is useful, but it largely restates what the schema provides. Since the schema carries most of the burden, a 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 a specific verb ('Run'), a specific resource type (Socrata SoQL query against a Santa Clara County Open Data dataset), and the key identifier (resource_id). This unambiguously distinguishes it from sibling tools like 'datasets' or 'metadata' that deal with dataset discovery rather than data retrieval.

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 the tool is for querying row-level data with filters and aggregations, which is distinct from sibling tools that list datasets or metadata. However, it does not explicitly name alternatives or state when NOT to use it (e.g., when only dataset discovery is needed), so it stops short of a 5.

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

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