Skip to main content
Glama
cesarvarela

Alpaca MCP Server

by cesarvarela

get-market-days

Retrieve trading market days within a specified date range using Alpaca MCP Server. Supports start and end date inputs to fetch accurate financial data efficiently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYes
startYes

Implementation Reference

  • index.ts:89-100 (handler)
    The main handler function for the 'get-market-days' tool. It makes an API request to the Alpaca calendar endpoint with start and end dates, returns JSON stringified market days on success, or an error message on failure.
    export async function getMarketDays({ start, end }: { start: string; end: string }) {
      try {
        const days = await request<any[]>({
          base: process.env.ALPACA_ENDPOINT!,
          path: "/v2/calendar",
          params: { start, end },
        });
        return { content: [{ type: "text", text: JSON.stringify(days) }] as any };
      } catch (err: any) {
        debug("get-market-days error", err);
        return { content: [{ type: "text", text: `Error fetching market days: ${err.message}` }] as any, isError: true };
      }
  • index.ts:149-153 (registration)
    Registration of the 'get-market-days' tool on the MCP server, including the tool name, inline Zod schema for input parameters (start and end as strings), and reference to the getMarketDays handler function.
    server.tool(
      "get-market-days",
      { start: z.string(), end: z.string() },
      getMarketDays
    );
  • Inline schema definition for the tool's input parameters using Zod: start and end as strings.
    { start: z.string(), end: z.string() },
    getMarketDays
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