Skip to main content
Glama

get_single_series

Retrieve U.S. labor statistics data for a specific time series from the Bureau of Labor Statistics for the past three years by providing a valid series ID.

Instructions

Retrieve data for a single BLS time series for the past three years. Provide a valid BLS series ID (uppercase letters, numbers, underscores, dashes, hashes only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
series_idYesBLS series ID, e.g. LAUCN040010000000005

Implementation Reference

  • The handler function for the get_single_series tool, which calls the client's getSingleSeries method.
    async ({ series_id }) => {
      try {
        const data = await client.getSingleSeries(series_id);
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      } catch (error) {
        return wrapError(error);
      }
    }
  • Tool registration for get_single_series using server.tool.
    server.tool(
      "get_single_series",
      "Retrieve data for a single BLS time series for the past three years. " +
        "Provide a valid BLS series ID (uppercase letters, numbers, underscores, dashes, hashes only).",
      {
        series_id: z
          .string()
          .regex(SERIES_ID_PATTERN, "Series ID must be uppercase with no special characters except _, -, #")
          .describe("BLS series ID, e.g. LAUCN040010000000005"),
      },
      async ({ series_id }) => {
        try {
          const data = await client.getSingleSeries(series_id);
          return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          return wrapError(error);
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the temporal scope ('past three years') and ID format constraints, but doesn't disclose behavioral traits such as rate limits, authentication needs, error handling, or what the returned data structure looks like (e.g., format, fields). This leaves significant gaps for a tool that retrieves data.

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 sentences, front-loaded with the core purpose and followed by parameter guidance. Every sentence earns its place by providing essential information without waste, making it efficient and easy to parse.

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

Completeness2/5

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

Given the complexity of a data retrieval tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., rate limits, auth), output format, and explicit usage guidelines compared to siblings. While concise, it doesn't compensate for the missing structured data, leaving the agent with insufficient context.

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?

The schema description coverage is 100%, so the schema already documents the single parameter 'series_id' with its pattern and example. The description adds value by specifying the ID format ('uppercase letters, numbers, underscores, dashes, hashes only'), but this is redundant with the schema's pattern. It doesn't provide additional semantic context beyond what the schema offers.

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 clearly states the action ('Retrieve data') and resource ('single BLS time series') with a specific temporal scope ('past three years'). It distinguishes from siblings like 'get_multiple_series' by specifying 'single', but doesn't explicitly differentiate from 'get_latest_series' or 'get_popular_series' in terms of scope or selection criteria.

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

Usage Guidelines3/5

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

The description implies usage by specifying 'single BLS time series' and 'past three years', which suggests when to use this tool (for individual series with historical data). However, it doesn't explicitly state when not to use it or name alternatives like 'get_multiple_series' for multiple series or 'get_latest_series' for only the latest data.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/larasrinath/bls_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server