Skip to main content
Glama

Connecticut Open Data

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral detail: returns top-N most relevant tools with full input schemas and curated examples, ready to call directly, and that it is a discovery tool, not a data retrieval tool.

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 well-structured, front-loading the main purpose, then listing domains, explaining return format, and giving usage guidance. Every sentence adds value without 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?

Given the tool's purpose (discovery) and no output schema, the description fully explains what is returned (names, descriptions, full schemas) and how to use it. It is complete for an agent to understand and invoke the tool correctly.

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 all parameters described. The description adds value by explaining the aliases for 'query' and providing examples of natural language inputs, as well as clarifying the limit parameter's purpose (top-N).

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 explicitly states the tool is for discovering/finding tools by describing data or task, listing many domains. It distinguishes itself from sibling tools which are various specialized query tools, making the unique purpose clear.

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 gives explicit guidance to 'Call this FIRST when you have many tools available and want to see the option set.' It implies when not to use (when you already know the tool) but does not list explicit alternatives or exclusions.

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