CREHQ MCP Server

crehq_datasets_list

Browse CREHQ's ready-to-license datasets filterable by category, country, and freshness. See row counts, schema, and refresh dates to find bulk data products.

Instructions

Browse CREHQ's catalog of packaged, ready-to-license datasets (whole-brand footprints, vertical rollups, FDD financials, etc.), filterable by category, country, and freshness. Each entry exposes row counts, schema, and refresh date — the menu of bulk data products.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crehq_datasets_list"
  }
}

Input Schema

Name	Required	Description
`country`	No	ISO country code filter.
`category`	No	Filter by category slug.
`per_page`	No	Results per page (max 200, default 50).
`freshness`	No	Freshness filter (e.g. '30d', '90d').

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. 'Browse' implies a read-only operation, and it mentions what entries expose (row counts, schema, refresh date), but it omits pagination behavior, authentication requirements, or rate limits. This is a clear but incomplete behavioral disclosure.

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-loaded with the tool's purpose, and contains no fluff. Every phrase adds value, including the examples and output fields.

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?

For a browse/list tool with optional filters and no output schema, the description explains what the data looks like (row counts, schema, refresh date) and the available filters. It is sufficient for an agent to understand the tool's role, though it could mention pagination (per_page) to be fully complete.

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 baseline is 3. The description mentions category, country, and freshness filters, which adds a contextual summary, but it does not add syntax or semantics beyond the schema. The per_page parameter is not mentioned in the description, so it adds marginal value.

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 browses CREHQ's catalog of packaged datasets, with examples (whole-brand footprints, vertical rollups, FDD financials) and explicitly calls it 'the menu of bulk data products', distinguishing it from sibling tools like crehq_purchased_datasets_list and crehq_locations_list.

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 implies usage for discovering available datasets before licensing, and the phrase 'menu of bulk data products' contrasts with purchase/download tools. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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