ipums-mcp

nhgis_get_time_series_table

Get complete metadata for any NHGIS time series table, including available years, geographic levels, and variable descriptions.

Instructions

Get full details for a specific NHGIS time series table including available years, geographic levels, and variable descriptions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>"
    },
    "name": "nhgis_get_time_series_table"
  }
}

Input Schema

Name	Required	Description	Default
`table`	Yes	Time series table identifier (e.g. 'CL8', 'B18')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It transparently states key output content (years, geographic levels, variable descriptions) and implies a read-only lookup via 'Get'. It does not discuss error conditions or permissions, but for a simple retrieval tool this is adequate and informative.

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 a single sentence that is front-loaded with the action and resource, followed by a concise enumeration of what 'full details' includes. No filler or redundant content.

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 getter tool with no output schema, the description is well-rounded: it states the input scope (specific table) and the expected return categories (years, geographic levels, variable descriptions). This gives an agent enough context to invoke the tool correctly without extra elaboration.

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 description coverage is 100%: the 'table' parameter has a clear description, pattern, and example. The tool description does not add additional parameter context, so it relies entirely on the schema. Per the baseline for high coverage, this is acceptable at a 3.

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 uses a specific verb ('Get full details') with a clear resource ('NHGIS time series table') and explicitly lists what details are included (years, geographic levels, variable descriptions). This distinguishes it from siblings like nhgis_list_time_series_tables (list discovery) and nhgis_search_time_series_tables (search).

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 provides clear context: use this when you need full details for a specific time series table. It does not explicitly name alternatives like search or list, but the 'specific table' wording implies that discovery tools should be used to find table identifiers first, making the intended usage reasonably clear.

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