Skip to main content
Glama
danielbres

massive-mcp

by danielbres

get_short_volume

Retrieve daily short-volume data for a stock ticker, with optional date filtering and pagination.

Instructions

Daily short-volume data for a ticker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesStock symbol.
date_gteNoInclusive lower bound on date.
limitNoMax rows. Default 30.
cursorNoPagination cursor.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function for the 'get_short_volume' tool. It takes ticker, date_gte, limit, and cursor parameters, and calls the Massive REST API at '/stocks/v1/short-volume' to return daily short-volume data.
    @mcp.tool()
    async def get_short_volume(
        ticker: str,
        date_gte: str | None = None,
        limit: int = 30,
        cursor: str | None = None,
    ) -> dict[str, Any]:
        """Daily short-volume data for a ticker.
    
        Args:
            ticker: Stock symbol.
            date_gte: Inclusive lower bound on date.
            limit: Max rows. Default 30.
            cursor: Pagination cursor.
        """
        return await client.get(
            "/stocks/v1/short-volume",
            {
                "ticker": ticker,
                "date.gte": date_gte,
                "limit": limit,
                "cursor": cursor,
                "order": "desc",
            },
        )
  • The 'register' function decorates the tool with @mcp.tool(), registering it with the FastMCP server. The registration happens inside a loop in server.py line 48 which calls financials.register(mcp, client).
    def register(mcp: FastMCP, client: MassiveClient) -> None:
        @mcp.tool()
        async def get_financials(
            ticker: str,
            timeframe: Timeframe = "quarterly",
            limit: int = 4,
            cursor: str | None = None,
        ) -> dict[str, Any]:
            """Financial statements (income, balance sheet, cash flow, ratios) for a ticker.
    
            Args:
                ticker: Stock symbol.
                timeframe: "annual", "quarterly", or "ttm". Default "quarterly".
                limit: Max periods returned. Default 4 (last year).
                cursor: Pagination cursor.
            """
            return await client.get(
                "/vX/reference/financials",
                {
                    "ticker": ticker,
                    "timeframe": timeframe,
                    "limit": limit,
                    "cursor": cursor,
                    "order": "desc",
                },
            )
    
        @mcp.tool()
        async def get_short_interest(
            ticker: str,
            settlement_date_gte: str | None = None,
            limit: int = 12,
            cursor: str | None = None,
        ) -> dict[str, Any]:
            """Bi-monthly short interest reports for a ticker.
    
            Args:
                ticker: Stock symbol.
                settlement_date_gte: Inclusive lower bound on settlement date.
                limit: Max rows. Default 12.
                cursor: Pagination cursor.
            """
            return await client.get(
                "/stocks/v1/short-interest",
                {
                    "ticker": ticker,
                    "settlement_date.gte": settlement_date_gte,
                    "limit": limit,
                    "cursor": cursor,
                    "order": "desc",
                },
            )
    
        @mcp.tool()
        async def get_short_volume(
            ticker: str,
            date_gte: str | None = None,
            limit: int = 30,
            cursor: str | None = None,
        ) -> dict[str, Any]:
            """Daily short-volume data for a ticker.
    
            Args:
                ticker: Stock symbol.
                date_gte: Inclusive lower bound on date.
                limit: Max rows. Default 30.
                cursor: Pagination cursor.
            """
            return await client.get(
                "/stocks/v1/short-volume",
                {
                    "ticker": ticker,
                    "date.gte": date_gte,
                    "limit": limit,
                    "cursor": cursor,
                    "order": "desc",
                },
            )
  • Imports and type alias used by the handler. MassiveClient (imported from ..client) provides the HTTP client with retry/auth logic used in the handler.
    from __future__ import annotations
    
    from typing import Any, Literal
    
    from fastmcp import FastMCP
    
    from ..client import MassiveClient
    
    Timeframe = Literal["annual", "quarterly", "ttm"]
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as data freshness, pagination behavior, or any rate limits. The schema implies pagination via cursor parameter, but the description omits this entirely.

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?

Very concise single sentence that front-loads the purpose. No wasted words, but no structured formatting (e.g., bullet points) that could help readability if more details were added.

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

Completeness2/5

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

Given the tool has 4 parameters (including pagination) and no annotations, the description is too brief. It does not explain the output, typical use, or pagination mechanics, leaving gaps for an AI agent.

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 all parameters. The description adds no additional meaning beyond what the schema provides; e.g., 'for a ticker' mirrors the schema description for ticker.

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 'Daily short-volume data for a ticker,' specifying the resource (short-volume data) and the target (ticker). This differentiates it from siblings like get_short_interest which focuses on short interest rather than volume.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives such as get_short_interest or get_snapshot. It does not mention prerequisites, typical use cases, or any conditions.

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

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/danielbres/Massive-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server