Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_obv

Calculate On Balance Volume (OBV) to analyze stock price momentum by tracking volume flow, helping identify potential trend reversals and confirm price movements.

Instructions

On Balance Volume (OBV)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe stock symbol (e.g., "IBM").
intervalYesTime interval (e.g., "daily", "60min", "weekly"). Check Alpha Vantage docs for valid intervals per indicator.
datatypeNoData format for the response.json
monthNoSpecific month for intraday intervals (YYYY-MM format).

Implementation Reference

  • src/index.ts:1117-1131 (registration)
    Registers the MCP tool 'technicalIndicators_obv' using server.addTool, specifying name, description, input schema, and an execute handler that calls the shared executeAvantageTool helper with the specific Alpha Vantage method av.technicalIndicators.obv.
    server.addTool({
      name: "technicalIndicators_obv",
      description: "On Balance Volume (OBV)",
      parameters: schemas.TechnicalIndicatorsCommonIndicatorParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_obv",
          args,
          context,
          (av, params) => av.technicalIndicators.obv(params)
        ),
    });
  • Zod schema defining the input parameters for the OBV tool: symbol, interval, optional datatype and month.
    export const TechnicalIndicatorsCommonIndicatorParamsSchema = z.object({
      symbol: z.string().describe('The stock symbol (e.g., "IBM").'),
      interval: z.string().describe('Time interval (e.g., "daily", "60min", "weekly"). Check Alpha Vantage docs for valid intervals per indicator.'),
      datatype: DatatypeSchema.default('json').optional(),
      month: z.string().optional().describe('Specific month for intraday intervals (YYYY-MM format).'),
    }).describe('Common parameters for many technical indicators.')
  • Shared handler function that implements the core logic for executing Alpha Vantage API calls for all tools, including OBV. Manages API keys, AVantage instances via resource manager, invokes the specific library method, and processes responses/errors.
    async function executeAvantageTool<TArgs, TResult>(
      toolName: string,
      args: TArgs,
      context: Context<Record<string, unknown> | undefined>, // Use the imported Context type directly
      avantageMethod: (
        av: AVantage,
        args: TArgs
      ) => Promise<{ error?: boolean; reason?: string; data?: TResult }>
    ): Promise<string> {
      logger.info(`Executing '${toolName}' tool for request ID: ${context}`);
      logger.debug(`Args for ${toolName}: ${JSON.stringify(args)}`);
    
      // --- Authentication & Resource Management ---
      // Access extraArgs safely - it might be null or undefined
      const extraArgsApiKey = context.extraArgs?.apiKey as string | undefined;
      const apiKey = extraArgsApiKey || config.apiKey;
    
      if (!apiKey) {
        logger.error(`'${toolName}' failed: Alpha Vantage API key missing.`);
        throw new UserError(apiKeyErrorMessage);
      }
      logger.debug(
        `Using AV API key (source: ${extraArgsApiKey ? "extraArgs" : "environment"}) for ${toolName}`
      );
    
      try {
        // Get or create AVantage instance managed by ResourceManager
        const av = await resourceManager.getResource<AVantage>(
          apiKey, // Cache key is the resolved API key
          "avantage_client", // Type identifier for logging
          async (key) => {
            // Factory Function
            logger.info(
              `Creating new AVantage instance for key ending ...${key.slice(-4)}`
            );
            // AVantage library reads AV_PREMIUM from process.env internally
            return new AVantage(key);
          },
          async (avInstance) => {
            // Cleanup Function (no-op needed for AVantage)
            logger.debug(`Destroying AVantage instance (no-op)`);
          }
        );
    
        // --- Library Call ---
        const result = await avantageMethod(av, args);
    
        // --- Response Handling ---
        if (result.error) {
          logger.warn(
            `'${toolName}' failed. Reason from avantage: ${result.reason}`
          );
          throw new UserError(result.reason || `Tool '${toolName}' failed.`);
        }
    
        if (result.data === undefined || result.data === null) {
          logger.warn(`'${toolName}' completed successfully but returned no data.`);
          return "null"; // Return string "null" for empty data
        }
    
        logger.info(`'${toolName}' completed successfully.`);
        // Stringify the data part of the response
        return JSON.stringify(result.data);
      } catch (error: any) {
        logger.error(
          `Error during execution of '${toolName}': ${error.message}`,
          error
        );
        // If it's already a UserError, rethrow it
        if (error instanceof UserError) {
          throw error;
        }
        // Otherwise, wrap it in a UserError
        throw new UserError(
          `An unexpected error occurred while executing tool '${toolName}': ${error.message}`
        );
      }
    }
  • Import of schemas module providing access to TechnicalIndicatorsCommonIndicatorParamsSchema used in the tool registration.
    import * as schemas from "./schemas.js"; // Import all schemas
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description provides zero information about what this tool actually does behaviorally - whether it fetches data, calculates indicators, requires authentication, has rate limits, returns time series data, or has any operational characteristics. It's completely opaque about the tool's behavior.

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

Conciseness2/5

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

While technically concise (just 3 words), this is under-specification rather than effective conciseness. The description fails to provide any meaningful information that would help an AI agent understand or use the tool. Every word should earn its place, but here the words don't provide operational value.

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

Completeness1/5

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

Given the complexity of financial data tools, no annotations, no output schema, and a description that provides only the tool's name, this is completely inadequate. The description fails to explain what OBV is, what it returns, how it differs from other indicators, or any context needed for proper tool selection and invocation.

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 4 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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

Purpose2/5

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

The description 'On Balance Volume (OBV)' is a tautology that merely restates the tool name without specifying what the tool does. It doesn't provide a verb or action, doesn't indicate this calculates or retrieves technical indicator data, and doesn't distinguish it from the many other technical indicator siblings in the list.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance about when to use this tool versus alternatives. With 60+ sibling tools including many other technical indicators, there's no indication of what makes OBV different from other volume-based indicators like AD or MFI, or when an agent should choose this particular technical analysis tool.

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/MissionSquad/mcp-avantage'

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