Skip to main content
Glama
Sign In

Bls

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Bls Search

bls_search
Read-onlyIdempotent

Search BLS economic data series by keyword. Returns matching series IDs and titles. Use bls_get_series with an ID to fetch historical data points.

Input Schema

NameRequiredDescriptionDefault
keywordYesKeyword to search for (e.g., "rent", "construction", "unemployment", "CPI", "housing")

Output Schema

NameRequiredDescriptionDefault
noteNoNote when no matches found
seriesYesMatching BLS series
keywordYesSearch keyword that was used
total_matchesYesNumber of matching series found

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "keyword": {
+      "description": "Search keyword that was used",
+      "type": "string"
+    },
+    "note": {
+      "description": "Note when no matches found",
+      "type": "string"
+    },
+    "series": {
+      "description": "Matching BLS series",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Series category (e.g., 'employment', 'housing', 'prices')",
+            "type": "string"
+          },
+          "description": {
+            "description": "Series description",
+            "type": "string"
+          },
+          "series_id": {
+            "description": "BLS series ID",
+            "type": "string"
+          },
+          "title": {
+            "description": "Series title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "series_id",
+          "title",
+          "category",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_matches": {
+      "description": "Number of matching series found",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "keyword",
+    "total_matches",
+    "series"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "keyword": "unemployment"
+  },
+  {
+    "keyword": "CPI inflation"
+  }
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that it returns matching series IDs and titles, which is consistent. No additional behavioral details are needed beyond 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?

The description is two short sentences, front-loads the purpose, and contains no filler. Every sentence adds value.

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

Completeness4/5

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

With an output schema (not shown) and rich annotations, the description is adequate. It could mention that the search is limited to BLS series or that multiple results may be returned, but overall it is sufficient for a simple search tool.

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% and the schema already documents the 'keyword' parameter with examples. The description does not add extra semantics beyond what the schema provides, so baseline 3 is appropriate.

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 'Search', the resource 'BLS economic data series', and the method 'by keyword'. It distinguishes from the sibling tool bls_get_series by specifying that it returns series IDs and titles.

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?

The description explicitly tells when to use this tool (to search by keyword) and when to use bls_get_series (to fetch historical data). However, it does not mention when to use alternatives like bls_latest or bls_popular_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
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