Skip to main content
Glama
Sign In
ApexVol MCP Server

ApexVol MCP Server

by ryansilk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Volume Profile

get_volume_profile
Read-only

Retrieve per-strike option volume and open-interest profiles to identify concentration levels, implied support/resistance, and notable OI changes for a ticker and expiration.

Instructions

Get the option volume and open-interest profile by strike.

Shows where volume and OI concentrate across strikes — support/ resistance implied by positioning, plus notable OI changes.

Use this tool when the user asks about:

  • Where the open interest sits

  • Volume by strike

  • OI-implied support and resistance

Args: ticker: Stock symbol expiration: Expiration date YYYY-MM-DD (default: nearest)

Returns: Per-strike volume/OI profile

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": {
      "ticker": "<ticker>"
    },
    "name": "get_volume_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
expirationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint already set to true, the description adds behavioral context about showing concentration, support/resistance, and notable OI changes. It also discloses the default expiration behavior, enhancing transparency beyond annotations.

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 tightly written with a clear structure: purpose, use cases, args, and returns. Every line adds value without redundancy, making it easy to parse.

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 tool's simplicity (2 parameters, no output schema), the description adequately covers purpose, inputs, and return format ('Per-strike volume/OI profile'). It provides enough contextual information for correct selection and invocation.

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

Parameters4/5

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

The description fully compensates for the 0% schema coverage by explaining each parameter: 'ticker: Stock symbol' and 'expiration: Expiration date YYYY-MM-DD (default: nearest)'. This adds meaningful semantics and default behavior beyond the schema.

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 it 'Get the option volume and open-interest profile by strike' with a specific verb and resource. It distinguishes itself from sibling tools by focusing on volume and open interest positioning, unlike chain or GEX tools.

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 lists 'Use this tool when the user asks about' with three concrete use cases, providing clear context for when to invoke it. It does not mention alternative tools or exclusions, but the usage context is unambiguous.

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

Deploy Server

Other Tools