Census County Business Patterns

compare_county_industries

Get a breakdown of all industries in a county.

Returns business pattern data for all 2-digit NAICS sectors in a
specific county. Useful for understanding the economic composition
of a community for grant narratives.

Args:
    state: Two-letter state abbreviation (e.g. 'CA', 'TX', 'NY').
    county_fips: 3-digit county FIPS code (e.g. '037' for Los Angeles County).
    year: Data year (default 2021). Available: 2012-2021.

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": {
      "state": "<state>",
      "county_fips": "<county_fips>"
    },
    "name": "compare_county_industries"
  }
}

Input Schema

Name	Required	Description	Default
`year`	No
`state`	Yes
`county_fips`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that data covers all 2-digit NAICS sectors and includes year range, but does not mention rate limits, auth requirements, or pagination. Adequate but not exhaustive.

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?

Description is concise (4 lines plus Args section), front-loaded with purpose, and structured in a clear 'what it does, what it returns, when to use' flow. The Args section is well-organized and adds value 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?

Output schema exists, so no need to document return values. Description covers purpose, usage context, and parameters thoroughly. Lacks mention of edge cases (e.g., large county performance) but sufficient for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description fully compensates. It clearly documents state format (two-letter abbreviation), county_fips format (3-digit code with example '037'), and year (default 2021, range 2012-2021). Every parameter is explained with concrete details.

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?

Description clearly states 'Get a breakdown of all industries in a county' and specifies returns business pattern data for all 2-digit NAICS sectors. It explains the purpose for grant narratives but does not explicitly differentiate from sibling tools like get_county_business_patterns or get_state_business_summary.

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 for understanding economic composition and grant narratives, but does not provide explicit when-to-use or when-not-to-use guidance, nor contrasts with sibling tools.

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

All Census County Business Patterns tools Inspect

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

Need Help?