Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

economicIndicators_realGDPPerCapita

Retrieve US Real GDP per Capita data to analyze economic productivity and standard of living trends for informed financial decisions.

Instructions

Retrieves US Real GDP per Capita data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datatypeNoData format for the response.json

Implementation Reference

  • src/index.ts:567-581 (registration)
    Registers the MCP tool 'economicIndicators_realGDPPerCapita' with description, input schema reference, and inline execute handler that delegates to the generic executeAvantageTool and AVantage library method.
    server.addTool({
      name: "economicIndicators_realGDPPerCapita",
      description: "Retrieves US Real GDP per Capita data.",
      parameters: schemas.EconomicIndicatorsDataTypeParamSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "economicIndicators_realGDPPerCapita",
          args,
          context,
          (av, params) => av.economicIndicators.realGDPPerCapita(params)
        ),
    });
  • Generic async handler function shared by all tools. Manages authentication, AVantage instance via resourceManager, executes the library method (av.economicIndicators.realGDPPerCapita for this tool), handles errors, and returns JSON stringified data.
    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}`
        );
      }
    }
  • Zod input validation schema for the tool. Accepts optional 'datatype' parameter (json or csv). Shared with other economic indicators.
    export const EconomicIndicatorsDataTypeParamSchema = z.object({
      datatype: DatatypeSchema.default('json').optional(),
    }).describe('Common parameter schema accepting only datatype.')
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Retrieves' implies a read-only operation, the description doesn't mention any behavioral traits like data freshness, source, rate limits, authentication requirements, or what format the data comes in beyond the parameter schema. For a data retrieval tool with zero annotation coverage, this is insufficient.

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 perfectly concise - a single sentence that states exactly what the tool does with zero wasted words. It's front-loaded with the core functionality and doesn't include any unnecessary information.

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?

For a data retrieval tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the returned data looks like, what time periods are covered, data granularity, or any limitations. With 100% schema coverage but no output schema, the description should compensate by explaining the response format and content.

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?

The schema description coverage is 100%, with the single parameter 'datatype' fully documented in the schema with enum values and default. The description adds no parameter information beyond what's already in the structured schema, so it meets the baseline expectation but doesn't provide additional value.

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 the verb ('Retrieves') and resource ('US Real GDP per Capita data'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar economic indicator tools like 'economicIndicators_realGDP' or 'economicIndicators_cpi', which would require sibling differentiation for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools available (including other economic indicators like 'economicIndicators_realGDP'), there's no indication of what makes this specific per capita data unique or when it should be preferred over other GDP or economic metrics.

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