ipums-mcp

nhgis_list_shapefiles

List available NHGIS shapefiles for boundary data. Retrieve identifiers for census geographies to include in extracts.

Instructions

List all available NHGIS shapefiles (boundary files). Returns identifiers for census geographies that can be included in extracts.

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_shapefiles"
  }
}

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/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the operation is a read-only list and specifies the return value. However, it does not mention pagination behavior despite the presence of pageSize and pageNumber parameters, nor any other behavioral nuances. This is a notable gap.

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 concise, consisting of two sentences. It is front-loaded with the verb and resource, and every sentence adds meaningful information without redundancy.

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?

Given the simplicity of the tool (no output schema, two optional parameters), the description adequately conveys the tool's purpose and return value. It lacks explicit mention of pagination, but overall it is sufficiently complete for an agent to select and invoke the tool correctly.

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 input schema provides 100% coverage of both parameters with descriptions. The tool description adds no additional semantic meaning beyond what the schema already conveys, so the baseline score of 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 specific action ('List all available NHGIS shapefiles') and the resource (shapefiles/boundary files). It also distinguishes itself from sibling tools by specifying that it returns identifiers for census geographies usable in extracts, making its purpose unambiguous.

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 implies a use case: to obtain identifiers for inclusion in extracts. It does not explicitly mention alternatives or exclusions, but the tool's name and the mention of using identifiers in extracts provide sufficient context for when to select this tool over other list tools.

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