Skip to main content
Glama

Ellimist

BLS series

data_macro_bls
Read-only

Use this to get U.S. Bureau of Labor Statistics series: CPI inflation, unemployment rate, payrolls, wages and other BLS series IDs (e.g. CUUR0000SA0, LNS14000000). Official public-domain data. Price: $0.005 USDC per call via x402 (no account). Not charged if it fails.

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": {
      "series_ids": "<series_ids>"
    },
    "name": "data_macro_bls"
  }
}

Input Schema

NameRequiredDescriptionDefault
series_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds non-obvious behavioral details: paid access at $0.005 USDC per call via x402, no account required, and no charge if the call fails. These are important operational traits beyond the annotations, though rate limits or data freshness are not covered.

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 tightly structured: purpose first, then data provenance, then pricing and failure policy. Every sentence provides useful information, with no redundant or filler content.

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 simple one-parameter read tool, the definition covers purpose, data source, pricing, and failure policy. However, it does not describe the return format (no output schema exists), and the parameter format is only conveyed by example, leaving some 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?

Schema description coverage is 0%, so the description would ideally carry the full burden of explaining the single parameter. It does clarify that series_ids are BLS series IDs and gives examples (CUUR0000SA0, LNS14000000), but those examples are already present in the schema. It does not explain the allowed pattern or the 1-to-25 item limit, limiting the added value.

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 states a specific verb ('get') and resource ('U.S. Bureau of Labor Statistics series'), with examples of what those series represent (CPI, unemployment, payrolls). It does not explicitly differentiate this tool from any sibling tools, so it falls short of a 5.

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

Usage Guidelines2/5

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

The only usage direction is 'Use this to get...', with no explicit when-to-use versus when-not guidance and no named alternatives among the many sibling macro data tools. This leaves the agent to infer the appropriate context for selecting this tool.

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