Skip to main content
Glama
Sign In
aigroup-finnhub-mcp

aigroup-finnhub-mcp

by jackdark425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

finnhub_alternative_data

Retrieve ESG scores, social sentiment, supply chain data, and patents for a stock symbol. Supports JSON export for large datasets.

Instructions

Access alternative data including ESG scores, social sentiment, and patents. Supports JSON export for large datasets.. Operations: get_esg_score, get_social_sentiment, get_supply_chain, get_patents

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "finnhub_alternative_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date in YYYY-MM-DD format (optional)
fromNoStart date in YYYY-MM-DD format (optional)
exportNoForce export to JSON file
symbolNoStock symbol
projectNoProject name for saving data
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so description must bear full burden. It mentions JSON export but fails to disclose side effects, rate limits, permissions, or what the export operation actually does (e.g., file creation).

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?

Concise two sentences plus a list; no fluff. The list of operations is somewhat redundant with the schema enum, but the JSON export note adds value.

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?

Despite listing operations, the description lacks details on return values, error handling, required permissions, and data freshness. With no output schema, more context is needed for a multi-operation tool.

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 coverage is high (83%), so baseline is 3. Description adds context about operations and export use cases but does not significantly enhance parameter meaning beyond the schema.

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

Purpose5/5

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

The description clearly identifies the tool as accessing alternative data (ESG, social sentiment, patents) and lists specific operations, distinguishing it from sibling tools like stock fundamentals or news.

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 vs alternatives like finnhub_stock_fundamentals or finnhub_news_sentiment. No when-not-to-use or prerequisite information provided.

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

Deploy Server

Other Tools