Skip to main content
Glama

Colorado Information Marketplace

by io.github.pipeworx-io

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Colorado Information Marketplace dataset by resource_id (e.g. "4ykn-tg5h"). 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. "4ykn-tg5h" (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": 100,
+    "resource_id": "4ykn-tg5h",
+    "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 indicate safe read operation. Description adds return format (JSON) and the nuance of omitting leading $ in SoQL clauses, providing behavioral details beyond annotations.

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, no redundancy, efficiently conveys purpose and parameters.

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 7 parameters, no output schema, the description explains the return format and key syntax rules. Could mention pagination behavior more, but overall adequate.

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?

All parameters have schema descriptions (100% coverage). Description reinforces the SoQL syntax rule and mentions limit/offset, but doesn't add much per-parameter detail. However, the note about omitting $ is valuable.

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?

Clearly states it runs a SoQL query on a Colorado dataset by resource_id, with filtering options. Distinguishes from siblings as the only direct query tool.

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?

Provides clear context that this tool is for querying specific datasets using SoQL syntax. Does not explicitly mention when not to use or alternatives, but the context is clear.

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

All Colorado Information Marketplace 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.

TDQS

A4/5.0
Disambiguation3/5

The tool set has several overlapping clusters: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded, entity_profile / recent_changes / compare_entities, and a half-dozen prediction-market tools. The descriptions are unusually detailed and mostly steer an agent correctly, but ask_pipeworx_beta is currently identical to ask_pipeworx and the prediction-market tools still require careful reading to pick the right one.

Naming Consistency3/5

All names are lowercase snake_case, but the conventions vary: many are verb_noun (resolve_entity, compare_entities, validate_claim), some are bare nouns (datasets, metadata, query), some are bare imperatives (remember, forget, subscribe), and there are separate prefix families like polymarket_* and pipeworx_*. It is readable and consistent in style, but not a single predictable pattern.

Tool Count2/5

34 tools exceeds the 25+ threshold for 'too many,' and the set is not tightly scoped: only datasets, metadata, and query directly relate to the stated Colorado Information Marketplace purpose. The bulk are Pipeworx data-research, prediction-market, memory, and subscription utilities, making the server feel like a broad platform bolted onto a state-data catalog.

Completeness4/5

For the core read-only lifecycle of the Colorado data catalog, search (datasets), schema inspection (metadata), and data retrieval (query) are covered. Minor gaps exist elsewhere: there is no explicit tool for fetching a pipeworx:// citation record directly, and some utilities like generate_llms_txt or scan_dependency are unrelated to the server's stated purpose, but most cited workflows can still complete.

Resources