Skip to main content
Glama
Skeego

opendata-mcp

by Skeego

search_datasets_v1_search_get

Search across datasets using full-text, semantic, or hybrid modes. Filter by provider, format, category, and status, with multiple sort options.

Instructions

GET /v1/search (public) — Search Datasets — Search across all datasets using full-text search.

Searches dataset names, descriptions, provider names, and column names. Results are ranked by relevance using PostgreSQL's FTS capabilities.

Search Modes:

  • keyword: Traditional FTS with tsvector matching

  • semantic: Embedding-based similarity search (conceptual matching)

  • hybrid: Combines both using Reciprocal Rank Fusion (RRF)

Query Syntax:

  • inflation - simple term search

  • "consumer price index" - exact phrase search

  • census -historical - exclude term

  • inflation OR unemployment - alternative terms

Sort Options:

  • relevance: FTS ranking (default when query provided)

  • recency: Most recently updated first

  • name: Alphabetical by dataset name

  • `populari…

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query. Supports Google-style syntax: quotes for phrases, - to exclude, OR for alternatives.
modeNoSearch mode: 'keyword' for FTS only, 'semantic' for embedding similarity, 'hybrid' for both combined with RRF fusion.
providerNoFilter by provider slug (e.g., 'bls', 'census')
formatNoFilter by data format (e.g., 'csv', 'json')
categoryNoFilter by category tag
statusNoFilter by dataset status. Defaults to 'ready' to show only queryable datasets.
sortNoSort order for results. Options: 'relevance' (FTS ranking), 'recency' (updated_at), 'name' (alphabetical), 'popularity' (stars), 'trending' (time-decayed activity), 'queries' (query count), 'downloads' (download count).
time_rangeNoTime range for period-based metrics (trending, queries, downloads). Options: 'today', 'week', 'month', 'year', 'all_time'. Defaults to 'week' for trending sort, 'all_time' otherwise.
limitNoMaximum number of results to return (1-100)
offsetNoNumber of results to skip for pagination
Behavior4/5

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

Discloses search behavior: uses PostgreSQL FTS, explains search modes (keyword, semantic, hybrid), query syntax, and sort options. With no annotations, the description carries the burden well, though response format is not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections for search modes, query syntax, sort options. Front-loaded with purpose. Minor issue: appears cut off at 'populari…', but otherwise concise for the detail provided.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers search behavior and parameter details well, but lacks description of pagination behavior (limit/offset), default status, response format, or authentication requirements. Adequate but with gaps for a 10-param tool with no output schema.

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%, but description adds meaning beyond schema by explaining search modes, query syntax, sort options with examples, and default for time_range. Adds value to parameter understanding.

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 searches datasets using full-text search across names, descriptions, provider names, and column names. Distinguishes from siblings like suggest_datasets_v1_search_suggest_get by specifying full search capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context about search modes and sort options, but no explicit guidance on when to use this tool over alternatives (e.g., suggest_datasets, list_datasets). Usage is implied but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Skeego/opendata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server