Skip to main content
Glama
newerton

Status Invest MCP Server

get-indicadores

Retrieves financial indicators for specified stock symbols. Use this tool to get key metrics for investment analysis.

Instructions

Buscar informações de indicadores de ações

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stocksYesArray of stock symbols

Implementation Reference

  • The tool handler for 'get-indicadores'. It registers the tool with MCP server (name 'get-indicadores', description 'Buscar informações de indicadores de ações'), accepts an array of stock symbols via Zod schema, and delegates to the service's getStockIndicators method.
    private registerGetIndicatorsToolHandler(): void {
      this.server.tool(
        'get-indicadores',
        'Buscar informações de indicadores de ações',
        {
          stocks: z.array(z.string()).describe('Array of stock symbols'),
        },
        async (args) => {
          const stocks: string[] = Array.isArray(args.stocks)
            ? args.stocks
            : [args.stocks];
    
          const infos = await this.service.getStockIndicators(stocks);
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(infos, null, 2),
              },
            ],
          };
        },
      );
  • The registerTools() method that registers all tool handlers, including registerGetIndicatorsToolHandler() for 'get-indicadores'.
    private registerTools() {
      this.registerGetStockToolHandler();
      this.registerGetIndicatorsToolHandler();
      this.registerGetStockPaymentDatesToolHandler();
      this.registerPortfolioAnalysisToolHandler();
    }
  • Schema definition for the 'get-indicadores' tool input: requires an array of stock strings.
    {
      stocks: z.array(z.string()).describe('Array of stock symbols'),
    },
  • The service method getStockIndicators() that fetches indicators for each stock by calling the API, then parses the HTML response using getResume() and getAllIndicators() helpers.
    async getStockIndicators(stocks: string[]) {
      const baseUrl = this.apiService.getUrlBase();
      const stockData = [];
      for (const stock of stocks) {
        const response = await this.apiService.getIndicators(stock);
        if (!response) continue;
    
        const resume = this.getResume(response);
        const indicators = this.getAllIndicators(response);
    
        const data = {
          stock: stock,
          url: `${baseUrl}/acoes/${stock.toLowerCase()}`,
          resume: {
            price: {
              value: resume.price.value,
              variation: resume.price.variation,
            },
            min52weeks: {
              value: resume.min52Weeks.value,
            },
            max52weeks: {
              value: resume.max52Weeks.value,
            },
            minMonth: {
              value: resume.minMonth.value,
            },
            maxMonth: {
              value: resume.maxMonth.value,
            },
            valuation12Months: {
              value: resume.valuation12Months.value,
            },
            valuationCurrentMonth: {
              value: resume.valuationCurrentMonth.value,
            },
          },
          indicators,
        };
    
        stockData.push(data);
      }
    
      return stockData;
    }
  • The API service method that fetches raw HTML for a stock's indicators page from statusinvest.com.br.
    async getIndicators(stock: string): Promise<string | null> {
      const data = await this.makeTextRequest<string>(
        `/acoes/${stock.toLowerCase()}`,
      );
      if (!data) return null;
      return data;
    }
Behavior2/5

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

Annotations are absent, so the description must carry the burden of behavioral disclosure. It only states 'search for stock indicator information' without mentioning any behavioral traits such as read-only, potential side effects, authentication needs, or performance implications. The agent cannot infer safety or side effects.

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 description is a single sentence, very concise. However, it may be too brief, lacking critical context. It earns a 4 because it is compact and to the point, but could be more informative without being verbose.

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 one parameter, no output schema, and no annotations, the description is incomplete. It does not specify the format of returned indicators, possible errors, or any constraints. The agent lacks sufficient context to fully understand the tool's behavior.

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 input schema covers the only parameter 'stocks' with a description 'Array of stock symbols'. The tool description adds no additional meaning beyond the schema. With 100% schema description coverage, baseline of 3 is appropriate.

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 states the tool searches for stock indicator information (verb 'buscar' + resource 'indicadores de ações'). It is clear and specific, but does not explicitly differentiate from sibling tools like 'get-acoes' or 'analise-carteira', which might have overlapping scope.

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 versus alternatives. The description does not mention any prerequisites, limitations, or alternatives like other tools for specific stocks or portfolio analysis.

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/newerton/mcp-status-invest'

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