Houston Open Data MCP

Get a Houston dataset

houston_get_dataset

Read-onlyIdempotent

Retrieve a Houston Open Data dataset by name or ID to get its description, owner, license, resources, queryable table IDs, and download URLs.

Instructions

Get a dataset's description, owner, license, and resources.

A dataset can hold several resources (for example one per year). Each resource reports queryable: when true, use its id with houston_describe_table and houston_query_records; when false, use its download_url. last_modified gives the resource's as-of date.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset": "<dataset>"
    },
    "name": "houston_get_dataset"
  }
}

Input Schema

Name	Required	Description	Default
`dataset`	Yes	Dataset `name` or `id` from a search result.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuine semantics beyond them: the dataset-to-resources one-to-many shape, the meaning of `queryable`, and that `last_modified` is the resource's as-of date rather than the dataset's.

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 core action leads, followed by a short paragraph on resource structure and the queryable branch. Every sentence carries operational information and there is no filler or repetition of the schema.

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?

An output schema exists, so return values need not be spelled out, and the description still explains the resource model that the output schema's `queryable` and `download_url` fields depend on. What is missing is minor: no note on what happens with an unknown or ambiguous dataset identifier.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that `dataset` is a name or id from a search result. The description adds nothing about that parameter (no id-vs-name behavior differences, no format hints), so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus the fields returned (description, owner, license, resources), which is far more than restating the name. It does not explicitly contrast itself with houston_search_datasets, so an agent must infer that search finds the dataset and this one expands it.

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?

Gives concrete downstream routing: if a resource reports `queryable: true`, use its `id` with houston_describe_table and houston_query_records; otherwise use `download_url`. That is real when-to-use guidance tied to named siblings, though it covers post-call branching rather than when to call this tool instead of the search tool.

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

Deploy Server