Skip to main content
Glama

regional-economy-brief

Regional Economy & Trade Brief — Given a US state, county or metro (name, FIPS or CBSA), an industry (NAICS code or description) and a role (retailer, logistics, cfo, lender, other), reads BLS LAUS and QCEW, FRED (state employment, house prices, goods exports and imports, regional CPI), Census Building Permits and USAspending live, then computes levels, year-over-year and three-year changes, location quotient, z-scores against th

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": {
      "region": "<region>",
      "industry": "<industry>",
      "role": "<role>"
    },
    "name": "regional-economy-brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesWho the brief is for.
regionYesA US state, county or metropolitan area by name ("Ohio", "Travis County, TX", "Phoenix metro"), state FIPS (39), county FIPS (48453) or metro CBSA code (38060).
industryYesNAICS code (44-45, 722, 4841) or a plain description ("restaurants", "trucking").
regionTypeNoDisambiguates a name that is both a county and a metro or state.
lookbackYearsNoYears of history used for z-scores (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose real behavioral context: that BLS LAUS/QCEW, FRED, Census Building Permits and USAspending are queried live, and that derived metrics (YoY, 3-year change, location quotient, z-scores) are computed rather than returned raw. It does not state latency, failure behavior when a source is unavailable, or what the returned artifact looks like, which matters for a fan-out live query across five sources with zero annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the purpose and every clause carries information, so there is little pure filler. But it is a single run-on sentence chaining inputs and metrics, and it ends truncated mid-word ('against the th'), which leaves the reader without a clean boundary between inputs and outputs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, no-output-schema tool that fans out over five live data sources, the description covers the input side and the headline derived metrics, but the truncation means the output picture is incomplete and no output format or structure is conveyed anywhere else. An agent knows roughly what it will get but not the shape or cost of the response.

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 the schema already documents every parameter including the role enum, region formats, regionType disambiguation and lookbackYears. The description restates the region/industry/role inputs and adds no syntax or default detail beyond them. With the schema doing the heavy lifting, the baseline of 3 is appropriate.

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?

The description names a specific deliverable (a regional economy & trade brief) and specifies the concrete inputs it accepts (US state, county or metro by name/FIPS/CBSA; industry by NAICS or description; role) plus the exact data sources it reads. It is clearly distinguishable from the two sibling briefs (infrastructure-pipeline-brief, regulatory-change-brief) by domain. It falls short of 5 only because the sentence trails off mid-thought, leaving the final computed metric set undefined.

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?

Usage is implied by the enumerated inputs: an agent can infer this is the tool for regional economic/trade analysis by geography and industry. However, there is no explicit statement of when to prefer this over the sibling briefs, no prerequisites (free-form names may need regionType disambiguation is only visible in the schema), and no mention of cost or latency for a live multi-source pull.

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