Skip to main content
Glama

Census

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Census Available Datasets

census_available_datasets
Read-onlyIdempotent

Discover Census datasets and their variables. Returns dataset names, descriptions, and variable codes (e.g., B25001_001E) for querying with other census tools.

Input Schema

NameRequiredDescriptionDefault
_apiKeyNoCensus API key (not required for this endpoint but accepted for consistency)

Output Schema

NameRequiredDescriptionDefault
datasetsYesHousing-related Census datasets
total_housing_relatedYesCount of housing-related datasets returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-census-api-key"
-  }
-]New value: +[
+  {}
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "datasets": {
+      "description": "Housing-related Census datasets",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Dataset description",
+            "type": "string"
+          },
+          "identifier": {
+            "description": "Dataset identifier code",
+            "type": "string"
+          },
+          "title": {
+            "description": "Dataset title",
+            "type": "string"
+          },
+          "vintage": {
+            "description": "Dataset vintage year if available",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "title",
+          "description",
+          "vintage",
+          "identifier"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_housing_related": {
+      "description": "Count of housing-related datasets returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_housing_related",
+    "datasets"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-census-api-key"
+  }
+]
  4. First observed

TDQS

A3.6/5.0
Behavior3/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/idempotency profile is covered. The description adds that an API key is not required for this endpoint, a useful behavioral note, but discloses nothing about caching, rate limits, or result size.

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?

Two compact sentences, front-loaded with the core purpose ('Discover Census datasets') followed by the concrete return contents and an example variable code. No wasted words.

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?

An output schema exists, so return values needn't be explained, and annotations cover behavior. The description adequately covers purpose and return scope for a zero-required-param discovery tool, though it could note when to reach for this versus the specific census_* data tools.

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% and the single parameter's own description already explains the API key is optional for this endpoint, so the description adds no parameter meaning. Baseline 3 applies when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Discover Census datasets and their variables') and clarifies the return contents. It distinguishes itself from data-fetching siblings like census_acs by being a metadata/discovery tool, though it doesn't name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage by stating the returned variable codes are 'for querying with other census tools,' which hints this is a preparatory step. But it gives no explicit when-to-use conditions, prerequisites, or named alternatives/ordering guidance.

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

All Census toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources