Skip to main content
Glama

get_popular_series

Retrieve the 25 most popular BLS series IDs for labor statistics, with optional filtering by specific survey abbreviations like LA, CU, or CE.

Instructions

Retrieve the 25 most popular BLS series IDs overall or for a specific survey. Optionally provide a survey abbreviation to filter by survey.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
surveyNoOptional 2-letter survey abbreviation, e.g. LA, CU, CE

Implementation Reference

  • The handler function for 'get_popular_series' which calls the underlying client method and formats the response.
    async ({ survey }) => {
      try {
        const data = await client.getPopularSeries(survey);
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      } catch (error) {
        return wrapError(error);
      }
    }
  • Registration of the 'get_popular_series' tool with its schema definition and handler.
    server.tool(
      "get_popular_series",
      "Retrieve the 25 most popular BLS series IDs overall or for a specific survey. " +
        "Optionally provide a survey abbreviation to filter by survey.",
      {
        survey: z
          .string()
          .regex(/^[A-Z]{2}$/, "Survey abbreviation must be exactly 2 uppercase letters")
          .optional()
          .describe("Optional 2-letter survey abbreviation, e.g. LA, CU, CE"),
      },
      async ({ survey }) => {
        try {
          const data = await client.getPopularSeries(survey);
          return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          return wrapError(error);
        }
      }
    );
  • The actual API implementation of getPopularSeries in the Client class.
    async getPopularSeries(survey?: string): Promise<unknown> {
      try {
        const response = await this.http.get("/timeseries/popular", {
          params: survey ? { survey } : undefined,
        });
        return response.data;
      } catch (error) {
        this.handleError(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 tool retrieves '25 most popular' items, which hints at a limit, but doesn't disclose other behavioral traits like rate limits, authentication needs, or what 'popular' means (e.g., based on views, downloads). This leaves gaps for a read operation.

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 a single, efficient sentence that front-loads the core purpose and includes the optional parameter detail without any wasted words. It's appropriately sized for the tool's simplicity.

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?

Given the tool's low complexity (1 optional parameter, no output schema, no annotations), the description covers the basic purpose and parameter use. However, without annotations or output schema, it lacks details on return values (e.g., format of the 25 series IDs) and behavioral context, making it adequate but with clear 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 100%, so the schema already documents the 'survey' parameter with its type, pattern, and example. The description adds minimal value by restating it's optional and for filtering, aligning with the baseline for high schema coverage.

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') and resource ('25 most popular BLS series IDs'), specifying scope ('overall or for a specific survey'). It doesn't explicitly differentiate from sibling tools like 'get_latest_series' or 'get_single_series', which is why it doesn't reach 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 Guidelines3/5

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

The description implies usage by mentioning the optional survey filter, but it doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_latest_series' or 'get_multiple_series'. No exclusions or prerequisites are stated.

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