Skip to main content
Glama

Data Sonoma

by io.github.pipeworx-io
OverviewAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Sonoma County Open Data dataset by resource_id (e.g. "3rsj-iche"). 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. "3rsj-iche" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 50,
+    "resource_id": "3rsj-iche",
+    "where": "year >= 2020"
+  }
+]
  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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it returns matching rows as JSON, which aligns with read-only behavior. It does not contradict annotations; it provides additional context on the return format and SoQL syntax, but could mention potential limits (e.g., max rows beyond default).

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: first states the core action, second adds filtering/return details. No superfluous words. The most important information is front-loaded and easy to parse.

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 the tool is a query operation with comprehensive annotations and schema, the description covers the main purpose and usage. It could be improved by mentioning that resource_id typically comes from the 'datasets' sibling tool, but it is still 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?

Schema coverage is 100% with good descriptions for each parameter. The description adds value by clarifying that SoQL clauses should omit the leading $ and by providing an example. This extra context justifies a score above baseline 3.

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 uses a specific verb 'Run' and identifies the resource as a 'Socrata SoQL query against a Sonoma County Open Data dataset by resource_id'. It clearly distinguishes from siblings like 'datasets' (which likely lists available datasets) by focusing on querying a specific dataset with SoQL syntax.

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 specifies how to filter using SoQL clauses and limit/offset, and includes an example. However, it does not explicitly state when to use this tool versus alternatives (e.g., searching vs querying). The guidance is clear but lacks explicit when-not-to-use or precondition references.

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

All Data Sonoma toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources