Skip to main content
Glama

Healthdata Get Dataset

healthdata_get_dataset
Read-onlyIdempotent

Full metadata for one HealthData.gov dataset by its Socrata id (a 4x4 like "g62h-syeh", returned by search_datasets). Returns title, description, owning agency, licence, every column with its type, row count and the last data update. NOTE: HealthData.gov migrated off CKAN, so an old CKAN package id or slug will NOT resolve, search for the dataset again to get its 4x4.

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": {
      "id": "g62h-syeh"
    },
    "name": "healthdata_get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSocrata 4x4, e.g. "g62h-syeh".

Output Schema

NameRequiredDescriptionDefault
idYesDataset package ID
urlNo
nameNoDataset name
tagsYesDataset tags/keywords
titleYesDataset title
agencyNo
columnsNo
createdNoDataset creation timestamp
licenseYesLicense type of the dataset
categoryNo
modifiedNoDataset last modified timestamp
rows_urlNo
resourcesNoArray of data resources (downloadable files)
created_atNo
descriptionYesFull dataset description
column_countNo
organizationNoOrganization that published the dataset
data_updated_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedOutput schema / properties / agency
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / column_count
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / columns
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "description": {
      +        "type": "string"
      +      },
      +      "field": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / created_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / data_updated_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / rows_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / url
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "title",
      -  "description",
      -  "organization",
      -  "license",
      -  "created",
      -  "modified",
      -  "tags",
      -  "resources"
      -]New value: +[
      +  "id",
      +  "title",
      +  "description",
      +  "license",
      +  "tags"
      +]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description adds real value beyond them by enumerating the returned fields and, more importantly, disclosing a failure mode — CKAN-era ids silently fail, requiring a re-search. It does not discuss rate limits or error payload shape, keeping it just under top marks.

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?

Three front-loaded sentences with no filler; the identifier format and the CKAN caveat both earn their place. The enumeration of return fields (title, description, agency, licence, columns) partially restates what the output schema already delivers, which is the only redundancy.

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

Completeness5/5

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

For a one-parameter lookup with an output schema and full annotation coverage, the description supplies everything needed: where the id comes from, what form it takes, what fails, and how to recover. Nothing material to a correct invocation is missing.

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% and the single parameter is already documented as a Socrata 4x4 with an example, so baseline is 3. The description adds provenance ('returned by search_datasets') and a negative constraint (CKAN ids/slugs won't work), which is meaning the schema does not carry.

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: 'Full metadata for one HealthData.gov dataset by its Socrata id.' It also pins the identifier format (a 4x4 like "g62h-syeh") and attributes provenance to search_datasets, so an agent can distinguish it from the search sibling without opening either schema.

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 clear context for use — call it with an id 'returned by search_datasets' — and an explicit exclusion: old CKAN package ids or slugs will NOT resolve, so re-search instead. It stops short of naming the row-fetching sibling (e.g. get_rows) as the alternative for actual data, so the guidance is strong but not fully exhaustive.

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.