Skip to main content
Glama

Alpaca

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Alpaca Intraday Vwap

alpaca_intraday_vwap
Read-onlyIdempotent

Current session VWAP for US stocks — is the price above or below VWAP right now? Fetches today's 1-minute bars from 04:00 ET (pre-market included), computes the cumulative volume-weighted average price, and compares it to the latest trade. Returns current_price, session_vwap, above_vwap, and session volume per symbol. Answers "current VWAP for BLK, AAPL, RHI, CTAS — above or below?" in one call. Multiple symbols comma-separated (max 20). BYOK Alpaca (free account), real-time IEX feed. Example: alpaca_intraday_vwap({ symbols: "BLK,AAPL,RHI,CTAS", _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. "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": "AAPL"
+  },
+  {
+    "_apiKey": "your-alpaca-api-key",
+    "symbols": "BLK,AAPL,RHI,CTAS"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description details that it fetches today's 1-minute bars from 04:00 ET (including pre-market), computes cumulative VWAP, and compares to the latest trade. It also notes the data source (BYOK Alpaca, real-time IEX feed). This adds significant behavioral context beyond the annotations (readOnlyHint, idempotentHint), which already indicate safety.

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, well-organized paragraph. It starts with the main purpose, explains the computation, lists return fields, and ends with an example. Every sentence adds value with no extraneous information.

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

Completeness5/5

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

Given the tool's moderate complexity, the description covers all essential aspects: what it does, how it works (data source, computation), inputs (symbols and API key with formatting), and outputs (listed fields). The rich annotations further complement the completeness. No output schema exists, but the description adequately explains return values.

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?

Both parameters are fully described in the input schema with clear descriptions. The description repeats the schema content for _apiKey and symbols, adding no new meaning. With 100% schema coverage, a baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool computes the current session VWAP for US stocks and compares it to the latest trade. It specifies exact verbs (fetches, computes, returns) and the resource (VWAP for given symbols). The purpose is distinct from sibling tools like alpaca_bars or alpaca_snapshot.

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

Usage Guidelines4/5

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

The description explicitly states that multiple symbols (comma-separated, max 20) can be queried in one call, and provides an example. However, it does not explicitly mention when not to use this tool or suggest alternatives for different timeframes or historical VWAP.

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