Skip to main content
Glama

Trading Signals Toolkit

VWAP + Bands

vwap_bands
Read-only

VWAP with standard-deviation bands from your OHLCV bars (session-anchored or full), z-score and band position. Read-only, never places orders. Informational only, not investment advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bars": "<bars>"
    },
    "name": "vwap_bands"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA timezone for sessions (default America/New_York)
barsYesOHLCV bars, oldest first: {t (ISO-8601 or epoch s/ms), o, h, l, c, v} or [t,o,h,l,c,v]. Max 5000.
bandsNoBand multipliers, default [1, 2]
anchorNosession (reset each tz date, default) or all
includeSeriesNoReturn the last 500 VWAP points

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so 'Read-only, never places orders' largely restates structured data. What does add value is that the computation is purely derived from user-supplied bars (no external fetch) and that the output is informational, though nothing is said about numerical edge cases like fewer than 2 bars or session-boundary handling.

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 substantive clause is front-loaded and dense, followed by two short safety sentences. The disclaimer sentence is boilerplate filler for an indicator tool but is short enough not to bloat the definition.

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?

With five well-documented parameters and no output schema, the description supplies the missing return-value signal (z-score and band position) and the computation's nature. It stops short of explaining output shape or ordering, but for a pure calculation tool that is a minor gap.

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 bars, tz, bands, anchor, and includeSeries in detail. The description only echoes the anchor modes via 'session-anchored or full' and adds no syntax or format detail beyond that, making the baseline 3 correct.

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 names a specific computation (VWAP with standard-deviation bands) over a specific input (your OHLCV bars) and states the derived outputs (z-score and band position). The parenthetical '(session-anchored or full)' distinguishes the two modes, and no sibling tool in the list computes VWAP, so an agent can route here without opening the schema.

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?

Usage is implied rather than stated: an agent infers 'use this when you need VWAP bands from bars you already hold.' There is a scope caveat ('Informational only, not investment advice') but no explicit when-not-to-use condition and no named alternative, so the agent gets context without routing rules.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources