Skip to main content
Glama

xpay✦ Finance Collection

getESGDisclosures

Align your investments with your values using the FMP ESG Investment Search API. Discover companies and funds based on Environmental, Social, and Governance (ESG) scores, performance, controversies, and business involvement criteria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It says the tool can 'Discover companies and funds' but does not state what the function actually returns, whether it is read-only, or any details about response structure or limitations. The glossy language obscures rather than clarifies behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but wastes the opening sentence on a vague value proposition ('Align your investments with your values'). The second sentence is weakly informative. It is under-specification rather than concise, earning a low score.

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 no output schema and no annotations, the description should at least clarify what data is returned for a symbol. It does not, leaving the agent with only a general sense that the tool is ESG-related. This is inadequate for selecting and invoking the tool correctly.

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% coverage for the 'symbol' parameter, described as 'Stock symbol'. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the verb 'Discover' and names the resource as 'companies and funds' related to ESG criteria, giving a vague sense of purpose. However, the tool name is 'getESGDisclosures' and the description does not explicitly mention 'disclosures' or 'retrieve ESG data for a symbol,' so it is unclear whether this returns data for a single symbol or performs a search.

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?

There is no guidance on when to use this tool versus alternatives like getESGRatings, getESGBenchmarks, or searchFundDisclosures. The description reads like a marketing pitch rather than functional instructions, leaving the agent without a clear decision-making basis.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources