Skip to main content
Glama
gangtiser

gangtise-mcp

by gangtiser

gangtise_foreign_opinion_list

Retrieve foreign institutional opinions from top brokers like Goldman Sachs and Morgan Stanley. Filter by stock, region, industry, rating, and date range.

Instructions

[当前日期 2026-05-27,当前年份 2026,时区 Asia/Shanghai。用户说"今天/最近/今年/当前"时按此日期换算,不要使用训练数据年份。] 查询外资机构观点列表(高盛、摩根士丹利等),支持按证券、地区、行业、券商、评级、时间范围筛选。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNo
startTimeNoYYYY-MM-DD HH:mm:ss。当前日期 2026-05-27,当前年份 2026
endTimeNoYYYY-MM-DD HH:mm:ss。当前日期 2026-05-27,当前年份 2026
keywordNo
rankTypeNo1=综合排序 | 2=时间倒序
regionListNo地区 ID,来自 gangtise_lookup type=regions
industryListNo
securityListNo
brokerListNo
ratingListNo
ratingChangeListNo
sizeNoMax rows (default 20 for paginated endpoints)
fetchAllNoFetch all pages; may be slow for large datasets
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states query and filtering capability, omitting details on pagination, rate limits, data freshness, or side effects.

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

Conciseness3/5

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

Relatively concise (two lines) with a necessary date reminder. However, the front-loaded date context seems misprioritized; tool purpose would be more appropriate first.

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?

With 13 parameters, no annotations, and no output schema, the description fails to cover return format, pagination behavior, or how to use lookup-dependent fields like regionList. Incomplete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 46%, leaving many parameters undescribed. The description lists some filter dimensions (security, region, industry, broker, rating, time) but does not explain specifics like ratingList or ratingChangeList. Inadequate compensation for low schema coverage.

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?

Clearly states it queries a list of foreign institution opinions (e.g., Goldman Sachs, Morgan Stanley) with multiple filter dimensions. Distinguishes from siblings like gangtise_foreign_report_list by focusing on opinions rather than reports.

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 explicit guidance on when to use this tool versus alternatives. Does not mention when not to use it or suggest other tools for similar tasks.

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/gangtiser/gangtise-mcp'

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