Skip to main content
Glama
Sign In

Data Piercecounty

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

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

Input 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. "hmbh-c3hw" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 50,
-    "resource_id": "hmbh-c3hw",
-    "where": "year >= 2020"
-  }
-]New value: +[
+  {
+    "limit": 20,
+    "resource_id": "hmbh-c3hw"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 50,
+    "resource_id": "hmbh-c3hw",
+    "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 readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral detail beyond that: SoQL clauses must be written without the leading '$', and the tool returns matching rows as JSON. No contradiction with the annotations exists.

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 three short, information-dense sentences. It front-loads the core purpose, then immediately gives the essential syntax constraint and output format, with no filler or repetition.

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 complete parameter documentation, read-only annotations, and a clear statement of the output format (JSON), the description provides what an agent needs to call it correctly. It covers the key SoQL clause set, the '$' omission rule, pagination parameters, and dataset identification. No major gap remains.

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 fully documents every parameter. The description adds only a high-level summary of available clauses (where/select/group/order plus limit/offset) and an example resource_id, which is useful but not meaningfully deeper than 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 uses a specific verb ('Run a Socrata SoQL query') and names a concrete resource type ('Pierce County Open Data dataset by resource_id'), with a real example id. It clearly distinguishes this tool from the sibling tools, none of which are about running SoQL queries.

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 makes the usage context clear: use it when you have a resource_id and need to run a SoQL query with filtering, grouping, ordering, or pagination. It does not explicitly name sibling alternatives like datasets or metadata or state when not to use query, so it loses one point for missing explicit exclusion guidance.

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

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