ipums-mcp

nhgis_list_datasets

Browse NHGIS datasets with pagination, returning dataset IDs, names, years, and geographic levels. Use pageSize and pageNumber to navigate results.

Instructions

Browse available NHGIS datasets. Returns paginated list of dataset identifiers, names, years, and geographic levels available.

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

Input Schema

Name	Required	Description	Default
`pageSize`	No	Results per page
`pageNumber`	No	Page number (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior ('Returns paginated list') and the exact fields returned, clearly indicating a read-only metadata listing. It does not cover auth or rate limits, but for a simple browse tool this is a reasonable level of transparency.

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 extremely concise, with only two sentences: the first states the purpose, the second states the output. Every word contributes value, and it is front-loaded with the primary verb and resource.

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 simple list tool with two optional parameters and no output schema, the description covers the essential aspects: what it does, what it returns, and the pagination behavior. It could mention default page size or that it returns only metadata, but these are minor gaps given the tool's simplicity.

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?

The schema already provides descriptions for both parameters ('Results per page' and 'Page number (1-based)'), and the description adds no additional parameter-level detail beyond noting pagination. Since schema coverage is 100%, baseline 3 is appropriate.

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's action ('Browse') and resource ('available NHGIS datasets'), and specifies the return content (dataset identifiers, names, years, geographic levels). This distinguishes it from sibling tools like nhgis_list_data_tables or nhgis_search_datasets, which have different scopes.

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 gives clear context for browsing datasets ('Browse available NHGIS datasets'), but it does not explicitly mention alternatives or when not to use it. It lacks the explicit exclusions or alternative tool references seen in higher-scoring examples, but the context is unambiguous.

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