Skip to main content
Glama
newerton

Status Invest MCP Server

get-acoes

Retrieve fundamental stock data for specified ticker symbols to analyze investment opportunities.

Instructions

Buscar informações básicas de ações

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stocksYesArray of stock symbols

Implementation Reference

  • Registers the 'get-acoes' MCP tool with Zod input schema and inline async handler that delegates to StatusInvestService.getStockResume and formats response as JSON text.
    private registerGetStockToolHandler(): void {
      this.server.tool(
        'get-acoes',
        'Buscar informações básicas 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.getStockResume(stocks);
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(infos, null, 2),
              },
            ],
          };
        },
      );
    }
  • Helper method in StatusInvestService that loops over stocks, fetches raw data from apiService.getStockResume, maps and enriches it (adds image URL, handles type), returns formatted array.
    async getStockResume(stocks: string[]) {
      const data = [];
      for (const stock of stocks) {
        const stockData = await this.apiService.getStockResume(stock);
        if (stockData && stockData?.length > 0) {
          for (const item of stockData) {
            let type = TypeEnum[item.type];
            if (!type) {
              type = `${item.type} unknown`;
            }
            const jsonData = {
              id: item.id,
              type,
              code: item.code,
              name: item.name,
              price: item.price,
              variation: item.variation,
              variationUp: item.variationUp,
              url: item.url,
              image: `https://statusinvest.com.br/img/company/avatar/${item.parentId}.jpg?v=214`,
            };
            data.push(jsonData);
          }
        }
      }
      return data;
    }
  • Core implementation: HTTP JSON fetch from StatusInvest API endpoint `/home/mainsearchquery?q={stock}` returning MainSearchQuery array.
    async getStockResume(stock: string): Promise<MainSearchQuery[] | null> {
      const data = await this.makeJsonRequest<MainSearchQuery[]>(
        `/home/mainsearchquery?q=${stock.toLowerCase()}`,
      );
      if (!data) return null;
      return data;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does ('search for basic stock information') without describing any behavioral traits such as whether it's read-only, rate-limited, authentication requirements, response format, or error handling. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'basic information' entails, how results are returned, or any limitations. For a tool that presumably returns financial data, this leaves significant gaps in understanding its behavior and output.

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 has 100% description coverage, with the 'stocks' parameter clearly documented as an array of stock symbols. The description doesn't add any meaning beyond this (e.g., it doesn't specify what 'basic information' includes or provide examples of valid symbols), so it meets the baseline score when the schema does the heavy lifting.

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 ('Buscar' - search) and resource ('informações básicas de ações' - basic stock information), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get-indicadores' (which might provide more detailed indicators) or 'get-acoes-datas-pagamento' (which focuses on payment dates), so it doesn't reach the highest 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. There are sibling tools like 'analise-carteira' (portfolio analysis), 'get-indicadores' (indicators), and 'get-acoes-datas-pagamento' (payment dates), but the description doesn't mention any of them or explain what makes this tool distinct for 'basic information'.

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