Skip to main content
Glama

Alpaca

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Alpaca Snapshot

alpaca_snapshot
Read-onlyIdempotent

Real-time US stock snapshot with extended-hours coverage: latest trade price, bid/ask quote, today's OHLCV, previous close, change and change % vs previous close, plus the latest minute bar with its VWAP — during pre-market and after-hours the minute bar IS the live extended-hours price. Answers "pre-market price of OKTA", "overnight change %", "after-hours volume and high/low". Multiple symbols comma-separated (max 20). BYOK Alpaca (free account), real-time IEX feed. Example: alpaca_snapshot({ symbols: "OKTA,AAPL", _apiKey: "key_id:secret_key" })

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesREQUIRED: your Alpaca credentials as "key_id:secret_key" — both halves joined by a colon. Free at alpaca.markets (a paper-trading account is enough for market data).
symbolsYesComma-separated ticker symbols, e.g. "OKTA" or "BLK,AAPL,RHI,CTAS" (max 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-alpaca-api-key",
+    "symbols": "OKTA"
+  },
+  {
+    "_apiKey": "your-alpaca-api-key",
+    "symbols": "BLK,AAPL,RHI,CTAS"
+  }
+]
  2. First observed

TDQS

A3.7/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, so the description's behavioral contribution is additive. It discloses that during extended hours the minute bar IS the live price, and specifies the data feed (real-time IEX). No contradictions with annotations.

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

Conciseness4/5

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

The description is a single paragraph that packs relevant details without excessive fluff. It begins with the core purpose and follows with specifics. It is slightly dense but remains efficient, earning a 4 rather than a 5 for slight verbosity.

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?

Given the lack of an output schema, the description covers the returned data fields comprehensively (trade, bid/ask, OHLCV, change, minute bar with VWAP). It also explains the extended-hours behavior and max symbols. It is mostly complete, though it could mention error handling or rate limits.

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%, so the description doesn't need to explain parameters in depth. It adds minimal extra context beyond the schema, such as the example format for _apiKey and the number of symbols. This meets the baseline for high-coverage schemas but doesn't significantly enhance meaning.

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 it provides a real-time US stock snapshot with extended-hours coverage, listing specific data points like OHLCV, previous close, and VWAP. It answers questions about pre-market prices and after-hours volume. However, it doesn't explicitly differentiate from sibling tools like alpaca_bars or alpaca_intraday_vwap, which slightly reduces clarity.

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 gives usage context by listing example queries it answers (e.g., 'pre-market price of OKTA'), implying when to use it. It also mentions the max 20 symbols. However, it does not provide explicit guidance on when not to use it or mention alternatives, so the usage guidelines are adequate but not detailed.

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

All Alpaca 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