Skip to main content
Glama
Houston Open Data MCP

Houston Open Data MCP

by Sandysmile

List Houston organizations

houston_list_organizations
Read-onlyIdempotent

Lists Houston Open Data publishing organizations and their dataset counts, so you can pick an organization name to filter dataset searches by department.

Instructions

List publishing organizations (departments) and their dataset counts.

Use an organization's name as the organization filter in houston_search_datasets.

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": "houston_list_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds modest value by mentioning that dataset counts are returned alongside each organization, but says nothing about result size, ordering, or pagination behavior.

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?

Two short sentences with no filler: the first states what is returned, the second states how to use the output. It is front-loaded and every clause carries information.

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 zero-parameter read-only list tool with a full output schema and complete annotations, the description supplies purpose and the crucial link to houston_search_datasets. The only meaningful gap is the lack of contrast with houston_list_groups, which matters because both appear in the sibling list.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline for a no-parameter tool applies. It still conveys the key field an agent will consume (`name`) for use in a sibling tool.

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?

The description uses a specific verb and resource ("List publishing organizations") and clarifies what an organization is by equating it to departments, plus notes that dataset counts are included. It does not, however, distinguish this tool from the sibling houston_list_groups, which an agent could easily confuse with an organization listing.

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?

It explicitly states the downstream workflow: take an organization's `name` and use it as the `organization` filter in houston_search_datasets, which is genuine when-to-use context. It gives no exclusions, such as when to use houston_list_groups instead.

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