Skip to main content
Glama

Healthdata Search Datasets

healthdata_search_datasets
Read-onlyIdempotent

Search HealthData.gov for public-health datasets by keyword (e.g. "COVID hospitalizations", "Medicare spending", "opioid prescriptions"). Returns each dataset's Socrata id (a 4x4 like "g62h-syeh"), title, description, owning agency, tags, when the data was last updated, and its page-view count. Pass the id to get_dataset for full metadata or to get_rows to read the actual rows.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "COVID-19 hospitalizations"
    },
    "name": "healthdata_search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-50 (default 10).
queryYesSearch query, e.g. "vaccination rates", "hospital readmissions".
offsetNoSkip this many results, for paging (default 0).

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of datasets matching the search query
resultsYesArray of matching datasets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / results / items / properties / agency
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / category
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / columns
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / results / items / properties / created_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / data_updated_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / page_views
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / results / items / properties / url
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "title",
      -  "description",
      -  "organization",
      -  "created",
      -  "modified",
      -  "tags",
      -  "num_resources",
      -  "resource_formats"
      -]New value: +[
      +  "id",
      +  "title",
      +  "description",
      +  "tags"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior4/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 covered. The description adds genuinely useful non-annotation context: the shape of the id (a Socrata 4x4 like "g62h-syeh") and the exact set of returned fields including last-updated timestamp and page-view count.

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?

Three sentences, front-loaded with the action and scope, then the return contract, then the next-step routing. No wasted preamble. The field enumeration is slightly long but each item tells the agent what it can key off of.

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 three-parameter discovery tool with a full output schema, the description covers purpose, query style, and downstream routing, which is what an agent needs to call it correctly. Minor gap: no mention of paging behavior despite limit/offset, though those are self-documented in the schema.

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 coverage is 100%, with query, limit, and offset each documented including defaults and ranges, so the schema does the heavy lifting. The description adds only that the query is keyword-style natural-language phrasing, illustrated by the parenthetical examples, which is a modest increment over the schema's own examples.

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?

States a specific verb and resource ("Search HealthData.gov for public-health datasets by keyword") and immediately grounds it with concrete query examples like "COVID hospitalizations" and "opioid prescriptions". It also distinguishes itself from the retrieval siblings by naming get_dataset and get_rows as downstream steps.

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?

Explicitly positions the tool as the discovery step and routes the agent forward: pass the returned id to get_dataset for metadata or get_rows for actual rows. It does not state exclusions, such as when to prefer search_within for searching inside an already-identified dataset, so the when-not half is missing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.