Skip to main content
Glama

get_company_by_symbol

Retrieve detailed company information using stock symbols from the Spanish stock exchange. Input a symbol to access financial data and corporate details.

Instructions

Get detailed information for a specific company by its stock symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol (e.g., SAN, TEF, IBE)

Implementation Reference

  • The tool handler implementation that extracts the symbol argument and delegates to the database method getCompanyBySymbol.
    case 'get_company_by_symbol':
      result = await this.db.getCompanyBySymbol((args as any)?.symbol);
      break;
  • Input schema defining the expected parameter 'symbol' as a required string.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: {
          type: 'string',
          description: 'Stock symbol (e.g., SAN, TEF, IBE)',
        },
      },
      required: ['symbol'],
    },
  • src/index.ts:59-72 (registration)
    Tool registration in the list of tools returned by ListToolsRequestSchema, including name, description, and input schema.
    {
      name: 'get_company_by_symbol',
      description: 'Get detailed information for a specific company by its stock symbol',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: {
            type: 'string',
            description: 'Stock symbol (e.g., SAN, TEF, IBE)',
          },
        },
        required: ['symbol'],
      },
    },
  • Database helper method that implements the core logic by fetching all companies and finding the one matching the symbol.
    async getCompanyBySymbol(symbol: string): Promise<any> {
      const companies = await this.getAllCompanies();
      return companies.find(company => company.symbol === symbol) || null;
    }
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. While 'Get detailed information' implies a read-only operation, it doesn't specify what 'detailed information' includes, whether there are rate limits, authentication requirements, error handling, or response format. This leaves significant gaps 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 with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the core purpose without unnecessary elaboration.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'detailed information' includes, how results are structured, or potential limitations. Given the complexity implied by sibling tools and the lack of structured data, more context is needed to guide effective use.

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 description mentions the parameter ('by its stock symbol') but adds minimal semantic value beyond what's in the schema, which has 100% coverage and clearly documents the 'symbol' parameter with examples. The baseline score of 3 is appropriate since the schema does the heavy lifting, though the description doesn't enhance understanding of parameter usage.

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 ('Get detailed information') and resource ('for a specific company'), specifying the lookup method ('by its stock symbol'). It distinguishes from siblings like 'get_all_companies' by focusing on a single company, but doesn't explicitly differentiate from other company-specific tools like 'get_company_directors' or 'get_company_shareholders'.

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 that also retrieve company-related data (e.g., 'get_company_directors', 'get_esg_scores', 'get_historical_prices'), there's no indication of what makes this tool distinct or when it should be preferred over others.

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/anbrme/ibex35-mcp-server'

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