Skip to main content
Glama
Sign In
stock-analyzer-mcp

stock-analyzer-mcp

by kevinlin49361128-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_market_sentiment

Read-onlyIdempotent

Analyzes market sentiment by combining FinBERT news sentiment and institutional flows, returning a sentiment index (0-100) with source breakdowns for more precise insights.

Instructions

取得市場情緒分析（結合 FinBERT 新聞情緒、法人動向），回傳情緒指數（0-100）和各來源細項。比 analyze_sentiment 更精確

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_market_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNo市場: TW 或 US，預設 TW

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, destructiveHint, and idempotentHint. The description adds behavioral context: it combines specific data sources (FinBERT and institutional movements) and returns a structured index and breakdown, providing transparency beyond annotations.

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 very concise with two sentences, front-loading the action and result. Every part is informative and not redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one optional parameter, no output schema), the description provides complete context: what it does, what it returns, and how it compares to a sibling. No gaps for this complexity level.

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?

With 100% schema description coverage for the single parameter 'market', the baseline is 3. The description does not add extra semantic meaning beyond what the schema already provides (market: TW or US).

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 states the tool's purpose: to get market sentiment analysis using FinBERT news sentiment and institutional movements, returning a sentiment index (0-100) and breakdown by source. It also distinguishes itself from the sibling 'analyze_sentiment' by claiming higher accuracy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly compares this tool to 'analyze_sentiment', suggesting it is more accurate, which guides when to use it over that alternative. However, it does not mention other potential alternatives or exclusions, but the context is clear.

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