Skip to main content
Glama

Bls

by io.github.pipeworx-io

Bls Popular Series

bls_popular_series
Read-onlyIdempotent

Browse popular BLS series by category: employment, inflation, wages, housing, productivity. Returns series IDs and descriptions. Start here to explore available data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category: housing, employment, prices, wages, productivity (optional, returns all if omitted)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoriesYesPopular series grouped by category
total_seriesYesTotal number of series in response
filter_categoryYesCategory filter applied, or null if none

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. Description adds that it returns series IDs and descriptions, but does not disclose other details like pagination or rate limits. Given annotations, this is adequate but not exceptional.

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, 20 words, front-loaded with essential information. No filler or redundancy. Highly efficient.

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?

With a single optional parameter, clear annotations, and assumed output schema, the description sufficiently covers all needed context: what, return types, and usage suggestion. No obvious gaps.

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?

Parameter schema description covers the parameter fully (100% coverage). Description lists categories slightly differently than schema, but adds no new semantic value beyond schema. Baseline 3 applies.

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?

Description uses verb 'browse' and specifies resource 'popular BLS series', indicating what it does and what it returns (series IDs and descriptions). It distinguishes from sibling tools like bls_get_series and bls_search by implying a high-level browsing function.

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

Usage Guidelines4/5

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

Explicitly says 'Start here to explore available data,' giving a clear entry-point context. However, it does not mention when not to use or directly reference alternatives among the sibling tools.

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

All Bls 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

A3.6/5.0
Disambiguation2/5

The ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded trio are nearly indistinguishable, with beta currently behaving identically to the stable version. Entity_profile, recent_changes, and compare_entities also overlap heavily as multi-source company research tools, and the six polymarket tools create additional boundary confusion.

Naming Consistency2/5

Most tools use snake_case, but there is no consistent verb_noun pattern: some are imperative phrases (ask_pipeworx, bls_get_series, resolve_entity), while others are noun phrases (entity_profile, pipeworx_feedback, polymarket_edges, recent_alerts). Even within the bls_* family, bls_latest breaks the verb pattern established by bls_get_series and bls_search.

Tool Count2/5

35 tools is well above the 25+ threshold for 'too many', and the server is named Bls yet only four tools actually serve BLS data. Most of the remaining tools cover unrelated domains like Polymarket arbitrage, memory, feedback, and general Pipeworx routing, making the count feel inflated for the apparent purpose.

Completeness3/5

The four BLS-specific tools cover search, browse, historical series fetch, and latest value, but there is no multi-series fetch or series metadata detail, which is a notable gap for a BLS-focused server. The broader Pipeworx toolset is extensive, but the lack of a coherent stated domain makes completeness hard to evaluate as a unified surface.

Resources