Skip to main content
Glama

Bls

by io.github.pipeworx-io

Bls Latest

bls_latest
Read-onlyIdempotent

Get the most recent data point for a BLS series. Returns latest value and date. Use when you need current figures without historical context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyNoBLS registration key (optional)
series_idYesBLS series ID (e.g., "LNS14000000")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesSeries title from catalog, or null if not found
latestYesMost recent data point
series_idYesBLS series identifier

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds minimal behavioral context beyond stating it returns latest value and date. No contradiction with 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 concise sentences: first states the action, second provides usage guidance. No extraneous text, front-loaded with key information.

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 tool's simplicity, annotations covering safety, full schema coverage, and presence of output schema, the description is complete for an agent to understand and use the tool correctly.

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 coverage is 100% with both parameters fully described. The description does not add additional semantic meaning beyond what the schema already provides.

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 'Get' and the resource 'most recent data point for a BLS series'. It distinguishes itself from sibling tools by specifying it retrieves the latest value without historical context.

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?

Explicitly says 'Use when you need current figures without historical context', providing clear guidance on when to use this tool over alternatives like bls_get_series.

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