Skip to main content
Glama

Business Dynamics Statistics Tool

business_dynamics_statistics_tool
Read-onlyIdempotent

Retrieve annual BDS on job creation, destruction, establishment births/deaths, and firm startups/shutdowns (1978-2023). Filter by geography, industry, firm age, and size to assess economic dynamism.

Instructions

Retrieve annual business dynamics statistics (BDS) showing job creation, job destruction, establishment births/deaths, and firm startups/shutdowns. Track economic dynamism and business health from 1978-2023 at national, state, and metro/micro area levels. Filter by industry (NAICS), firm age, firm size, establishment age, and establishment size. Essential for understanding business environment, entrepreneurship rates, and economic vitality when evaluating areas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesYear for BDS data (1978-2023)
variablesNoVariables to retrieve. Common: ESTABS (establishments), ESTABS_ENTRY (new establishments), ESTABS_EXIT (closing establishments), JOB_CREATION (gross jobs created), JOB_DESTRUCTION (gross jobs destroyed), NET_JOB_CREATION (net job change), FIRMS (number of firms), FIRMS_ENTRY (new firms), FIRMS_EXIT (closing firms), EMP (employment), DENOM (denominator for rates), JOB_CREATION_BIRTHS (job creation from births), JOB_CREATION_CONTINUERS (job creation from expanding firms), JOB_CREATION_RATE (job creation rate), JOB_DESTRUCTION_DEATHS (job destruction from deaths), JOB_DESTRUCTION_CONTINUERS (job destruction from contracting firms), JOB_DESTRUCTION_RATE (job destruction rate)
geographyNoGeographic level: us (national), state (state), metro (metropolitan/micropolitan statistical area)state
stateNoState FIPS code (required for metro geography, optional for state)
naicsNoNAICS 2012 industry code. Examples: "00" (all), "11" (agriculture), "23" (construction), "31-33" (manufacturing), "42" (wholesale trade), "44-45" (retail trade), "51" (information), "52" (finance), "53" (real estate), "54" (professional services), "55" (management), "56" (administrative), "61" (educational), "62" (healthcare), "71" (arts/entertainment), "72" (accommodation/food), "81" (other services)
metroNoMetro filter: 0 (all), 1 (filter applied), M (metropolitan), N (micropolitan/non-metro)
geocompNoGeographic component: A0 (all), C1 (Metro/Micro Central County), O1 (Metro/Micro Outlying County)
sicNoSIC code flag: 0 (NAICS), 1 (SIC 1987)
fage4NoFirm age: a) 0 (startups), b) 1-5, c) 6-10, d) 11-15, e) 16-20, f) 21-25, g) 26+, h) Left Censored
fsizeNoFirm size by employment: a) 1-4, b) 5-9, c) 10-19, d) 20-49, e) 50-99, f) 100-249, g) 250-499, h) 500-999, i) 1000-2499, j) 2500-4999, k) 5000-9999, l) 10000+
eage4NoEstablishment age: a) 0 (new), b) 1-5, c) 6-10, d) 11-15, e) 16-20, f) 21-25, g) 26+, h) Born before 1976, i) Left Censored
esizeNoEstablishment size by employment: a) 1-4, b) 5-9, c) 10-19, d) 20-49, e) 50-99, f) 100-249, g) 250-499, h) 500-999, i) 1000-2499, j) 2500+
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by specifying the data scope (annual, national/state/metro, filters) and the fact that it retrieves historical data from 1978-2023. No contradictions, and it provides context beyond annotations.

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 sentences, front-loaded with the key action and resource. Every sentence adds value: first sentence defines the tool, second explains filters and use case. No unnecessary 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?

Given 12 parameters and no output schema, the description adequately covers the data types, time range, geography, and filters. It also states the tool's essential use. It could mention the return format or behavior when no variables are specified (schema has defaults), but overall it is complete enough for effective tool selection.

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%, so baseline is 3. The description mentions filtering by NAICS, firm age, etc., but these are already detailed in the input schema. No additional semantic information about parameters is provided beyond what the schema offers.

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 verb 'Retrieve' and resource 'annual business dynamics statistics (BDS)', lists specific data types (job creation, destruction, births/deaths) and specifies the data source (BDS) and time range (1978-2023). This distinguishes it from sibling tools like annual_business_survey_tool or county_business_patterns_tool, which cover different datasets.

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 economic analysis ('essential for understanding business environment, entrepreneurship rates, and economic vitality') but does not explicitly state when not to use this tool or compare it to alternatives. No exclusions or alternative tool names are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mattpodwysocki/census-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server