Skip to main content
Glama

get_esg_scores

Retrieve ESG scores for companies to assess environmental, social, and governance performance in the Spanish stock market.

Instructions

Get ESG (Environmental, Social, Governance) scores

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNoOptional: Company ID to filter by

Implementation Reference

  • The handler case in the CallToolRequestSchema handler that processes 'get_esg_scores' tool calls by extracting the optional companyId argument and delegating to DatabaseManager.getESGScores.
    case 'get_esg_scores':
      result = await this.db.getESGScores((args as any)?.companyId);
      break;
  • Input schema for the get_esg_scores tool, defining an optional companyId parameter.
    inputSchema: {
      type: 'object',
      properties: {
        companyId: {
          type: 'string',
          description: 'Optional: Company ID to filter by',
        },
      },
    },
  • src/index.ts:301-313 (registration)
    Registration of the 'get_esg_scores' tool in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'get_esg_scores',
      description: 'Get ESG (Environmental, Social, Governance) scores',
      inputSchema: {
        type: 'object',
        properties: {
          companyId: {
            type: 'string',
            description: 'Optional: Company ID to filter by',
          },
        },
      },
    },
  • Implementation of getESGScores in DatabaseManager, which currently returns an empty array as ESG data is not available in the API.
    async getESGScores(companyId?: string): Promise<any[]> {
      return []; // ESG data not available in current worker API
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the action 'Get' without disclosing behavioral traits such as whether it's a read-only operation, requires authentication, has rate limits, or what the return format looks like. 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 with zero waste, front-loaded with the core action. It's appropriately sized for a simple tool, making it highly concise and well-structured.

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's complexity (a data retrieval tool with no annotations and no output schema), the description is incomplete. It lacks details on return values, error handling, or behavioral context, which are crucial for an AI agent to use it correctly, especially with many sibling tools available.

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 the single parameter 'companyId' as optional. The description adds no additional meaning beyond what the schema provides, such as explaining what ESG scores include or how filtering works, but baseline 3 is appropriate when 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 'Get' and the resource 'ESG (Environmental, Social, Governance) scores', making the purpose specific and understandable. However, it doesn't differentiate from siblings like 'get_all_companies' or 'get_company_by_symbol', which might also retrieve company data, 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. With siblings like 'get_all_companies' or 'compare_companies' that might relate to ESG data, there's no explicit mention of context, exclusions, or prerequisites, leaving usage unclear.

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