Skip to main content
Glama

Connecticut Open Data

by io.github.pipeworx-io

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a Connecticut Open Data dataset by resource_id (e.g. "28fr-iqnx"). 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. "28fr-iqnx" (from datasets).

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive behavior. The description adds that it returns JSON, but does not contradict annotations. Additional behavioral context beyond annotations is minimal.

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 sentences, front-loading the core purpose. Every sentence is informative and there is no redundant wording.

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?

Despite no output schema, the description states the return format (JSON rows). Examples in the input schema provide further clarity. Completeness is high for a query tool.

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 each parameter. The description adds no new parameter semantics beyond mentioning SoQL clauses and examples.

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 the tool runs a SoQL query against a Connecticut Open Data dataset using a resource_id, and lists filtering clauses. This is specific and distinguishes it from sibling tools like 'datasets' or 'metadata'.

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 explicit guidance on using SoQL clauses without the leading $, and includes examples. However, it does not explicitly state when not to use this tool or mention alternatives among sibling tools.

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

All Connecticut Open Data 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

A3.5/5.0
Disambiguation1/5

Multiple tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) have overlapping research purposes. Additionally, many Polymarket and Pipeworx-specific tools are unrelated to the Connecticut Open Data server name, causing confusion.

Naming Consistency2/5

Naming is highly inconsistent: some use snake_case (ask_pipeworx, resolve_entity), others use longer descriptive phrases (polymarket_fill_risk, scan_competitor_ai_presence), with no clear pattern.

Tool Count1/5

The server claims to be about Connecticut Open Data but includes 34 tools, only 3 of which (datasets, metadata, query) are relevant. The vast majority are unrelated Pipeworx/Prediction Market tools, making the size inappropriate.

Completeness1/5

For Connecticut Open Data coverage, only basic dataset search, metadata, and query tools exist. Missing common operations like data upload, schema modification, or API key management for the open data portal.

Resources