Skip to main content
Glama

BRAINIAC Geo & Environment Lookups

Look up US ACS demographics

geo-environment_us-acs-demographics
Read-onlyIdempotent

Return selected ACS 2020–2024 5-year estimates and margins of error for a US state, county or ZCTA. Price $0.03 USDC. POST /api/v1/geo-environment/us-acs-demographics. An unpaid call returns the x402 payment terms and does not run.

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": {
      "geography": "<geography>",
      "code": "<code>"
    },
    "name": "geo-environment_us-acs-demographics"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYescode, string, length 1 to 10. Required.
geographyYesgeography, string, one of state, county, zcta. Required.

Output Schema

NameRequiredDescriptionDefault
geoIdNogeoId. String.
valuesNovalues. Object.
sourcesNosources. Array.
vintageNovintage. String.
geographyNogeography. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower, and the description still adds real operational context: a $0.03 USDC price, the x402 payment flow, and the fact that an unpaid call returns payment terms rather than data. It stops short of saying what 'selected' estimates are returned, how large responses are, or whether the payment output is an error or a normal response body.

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?

Three short sentences, front-loaded with the data returned, followed by cost and the payment failure mode. No filler, no restatement of the title, and the endpoint path is compactly included.

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 shape need not be described, and the read-only, idempotent annotations plus the payment disclosure cover the main behavioral risks for a two-parameter lookup. The remaining hole is the format of 'code' and the meaning of 'selected' estimates, which leaves an agent slightly under-informed before calling.

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%, so the schema itself documents both parameters, making 3 the baseline. The description does map the 'geography' enum to real entity types (state, county, ZCTA), which is mild added meaning, but it never explains what 'code' should contain — FIPS, ZIP, or a name — even though its 1–10 character limit leaves that genuinely ambiguous.

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 ('Return selected ACS 2020–2024 5-year estimates and margins of error') plus the exact geographic grain (state, county, ZCTA). That is immediately distinguishable from the earthquake, fire, GTFS and sun-position siblings without opening any schema.

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?

The description implies usage by enumerating the supported geography levels, but gives no explicit when-to-use or when-not guidance and names no alternative. It does not say, for example, that a ZIP-level question requires 'zcta' rather than 'county', or which sibling to use for non-ACS data.

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.

Resources