Skip to main content
Glama
Sign In

BLS OEWS

by com.1102tools
OverviewDiscussionsAdmin

list_common_metros

Read-only

List common metro area MSA codes for wage lookups.

Use these codes with get_wage_data(scope='metro', area_code=...).
Pass the 5-digit MSA code (the tool auto-pads to 7 characters).

For the full MSA list: https://www.bls.gov/oes/current/msa_def.htm

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_common_metros"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, non-open-world lookup. The description adds useful behavioral context by clarifying that this returns a curated 'common' subset rather than the full MSA list.

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?

The description is three short, front-loaded sentences with no filler. The purpose, downstream usage, code format, and full-list reference are all presented efficiently.

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

Completeness5/5

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

Given the empty input schema, existing output schema, and read-only annotations, the description covers what an agent needs: what the tool returns, how to use the codes, and where to find the complete list.

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

Parameters4/5

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

This tool takes no parameters, so the schema provides no parameter semantics to clarify. The description still adds useful integration context by explaining that the MSA code is 5 digits and is auto-padded to 7 characters when passed to get_wage_data.

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 states a specific verb and resource: it lists common metro area MSA codes, and it immediately scopes them to wage lookups. The word 'common' also distinguishes this from the full MSA list, which is linked separately.

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

Usage Guidelines5/5

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

It explicitly tells the agent to use the returned codes with get_wage_data(scope='metro', area_code=...), and it points to the BLS page when the full MSA list is needed. This gives clear when-to-use guidance and an alternative for broader coverage.

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

All BLS OEWS 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