Skip to main content
Glama
cesarvarela

Alpaca MCP Server

by cesarvarela

get-news

Retrieve financial news data by specifying date range and stock symbols using the Alpaca MCP Server tool for market analysis and insights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYes
startYes
symbolsYes

Implementation Reference

  • The handler function for the 'get-news' tool. It fetches news from the Alpaca API for specified symbols within a date range, handling pagination and returning JSON-formatted news articles or an error message.
    export async function getNews({ start, end, symbols }: { start: string; end: string; symbols: string[] }) {
      try {
        const all: any[] = [];
        let pageToken: string | undefined;
        do {
          const params: Record<string, unknown> = pageToken
            ? { page_token: pageToken }
            : { sort: "desc", start, end, symbols: symbols.join(","), include_content: true };
          const resp = await request<{ news: any[]; next_page_token?: string }>({
            base: process.env.ALPACA_ENDPOINT!,
            path: "/v1beta1/news",
            params,
          });
          all.push(...resp.news);
          pageToken = resp.next_page_token;
        } while (pageToken);
        return { content: [{ type: "text", text: JSON.stringify(all) }] as any };
      } catch (err: any) {
        debug("get-news error", err);
        return { content: [{ type: "text", text: `Error fetching news: ${err.message}` }] as any, isError: true };
      }
    }
  • index.ts:155-159 (registration)
    Registration of the 'get-news' tool using McpServer.tool, specifying the name, input schema with Zod validation, and referencing the getNews handler function.
    server.tool(
      "get-news",
      { start: z.string(), end: z.string(), symbols: z.array(z.string()) },
      getNews
    );
  • Zod schema defining the input parameters for the 'get-news' tool: start and end dates as strings, and an array of symbol strings.
    { start: z.string(), end: z.string(), symbols: z.array(z.string()) },
  • Helper function 'request' used by getNews to make authenticated API calls to Alpaca endpoints.
    async function request<T>({ base = process.env.ALPACA_ENDPOINT!, path, method = "GET", params = {} }: RequestOptions): Promise<T> {
      if (!process.env.ALPACA_API_KEY || !process.env.ALPACA_SECRET_KEY) {
        throw new Error("Alpaca credentials not configured. Set ALPACA_API_KEY and ALPACA_SECRET_KEY.");
      }
    
      const qs = new URLSearchParams(params as Record<string, string>).toString();
      const url = `${base}${path}${qs ? `?${qs}` : ""}`;
    
      const res = await fetch(url, {
        method,
        headers: {
          "APCA-API-KEY-ID": process.env.ALPACA_API_KEY!,
          "APCA-API-SECRET-KEY": process.env.ALPACA_SECRET_KEY!,
        },
      });
      if (!res.ok) {
        const err = await res.json();
        throw new Error(`${res.status} ${res.statusText} - ${JSON.stringify(err)}`);
      }
      return (await res.json()) as T;
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/cesarvarela/alpaca-mcp'

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