Skip to main content
Glama

bls-labor-mcp-server

by io.github.cyanheads

Get Latest BLS Observation

bls_get_latest
Read-onlyIdempotent

Return the single most recent observation for one or more BLS series. Use for "what is X right now" questions — the current unemployment rate, the latest CPI reading, etc. Each series consumes one API query against the 500/day limit; for the current value of many series, bls_get_series with a 1-year window is more quota-efficient (one query for up to 50 series). Recommended limit: 10 series; maximum: 50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
series_idsYesOne or more BLS SeriesIDs (1–50). Each consumes one daily API query. Use bls_search_series to resolve concepts to SeriesIDs. Recommended: ≤10 series.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
failedNoSeries that failed to fetch. Inspect seriesId and error for per-item details. Not-found series appear here rather than as a tool-level error.
noticeNoGuidance when one or more series failed — e.g. to use bls_search_series to verify SeriesIDs. Absent when all series returned data.
resultsNoSuccessfully fetched series with their latest observations. Series that failed appear in failed[] instead.
succeededNoNumber of series with a successfully fetched observation.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, and idempotent traits, lowering the burden on the description. The description adds useful behavioral context beyond annotations: each series consumes one API query against the 500/day limit and the tool returns only the single most recent observation. This goes beyond the structured metadata without contradicting it.

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 four sentences with no filler, front-loading the core function first, then use case, quota behavior, and the alternative path. Every sentence earns its place and directly helps an agent decide whether and how to invoke the tool.

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?

For a single-parameter tool with an output schema and safety annotations, the description covers everything needed: what it returns, when to use it, quota implications, limits, and when to prefer an alternative. Nothing critical is missing.

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 baseline is 3. The tool description restates quota and limit information already present in the schema description but does not materially add new parameter-level meaning. The schema fully documents series_ids, min/max, and the per-query cost, so no additional compensation is needed.

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: 'Return the single most recent observation for one or more BLS series.' It is immediately clear how this differs from sibling tools, especially bls_get_series, which the description explicitly contrasts. No ambiguity remains about what the tool does.

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?

The description explicitly assigns this tool to 'what is X right now' questions and advises using bls_get_series with a 1-year window when many series are needed for quota efficiency. It also provides recommended and maximum series counts, giving the agent concrete selection criteria.

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

All bls-labor-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool serves a distinct purpose: searching, listing, fetching, describing, and querying. No overlap between tools like bls_get_latest and bls_get_series, which have clear scope differences.

Naming Consistency5/5

All tools follow the bls_verb_noun pattern in snake_case, e.g., bls_search_series, bls_get_latest, bls_dataframe_query. Consistent and predictable.

Tool Count5/5

Six tools cover the essential workflow: discovery (list, search), retrieval (get_latest, get_series), and analysis (describe, query). Neither too few nor too many.

Completeness4/5

Covers the full read lifecycle from discovery to analysis. Minor gaps like a dedicated metadata tool for specific series, but search_series returns sufficient info. Overall well-scoped.

Resources