Skip to main content
Glama
lj22503

InvestBrain

rag_rag_search_reports

Search brokerage research reports by semantic query to retrieve recent summaries with institution, stock, industry, rating, and earnings forecast details.

Instructions

搜索券商研报——基于语义向量检索。

返回最近入库的券商研报摘要,包含机构、股票、行业、评级、盈利预测等信息。

Args:
    query: 搜索关键词(如"宁德时代 业绩"、"保险 增长"、"半导体")
    top_k: 返回结果数量,默认5

Returns:
    {
        "query": str,
        "count": int,
        "results": [
            {
                "info_code": str,
                "title": str,
                "org_name": str,
                "stock_name": str,
                "stock_code": str,
                "industry_name": str,
                "rating": str,
                "rating_change": str,
                "publish_date": str,
                "text": str,
                "distance": float,
            }
        ]
    }

Input Schema

NameRequiredDescriptionDefault
queryYes
top_kNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that results are limited to recently ingested reports (最近入库) and that each hit carries a distance/similarity score, but it omits auth requirements, result caps, and whether the corpus is date-bounded.

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?

Front-loaded with the one-line purpose, then Args and Returns in a scannable structure. The Returns block is long but justified since no output schema exists; nothing is wasted, though the block could be trimmed to field names.

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

Completeness4/5

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

With no output schema and no annotations, the description does the heavy lifting well: it documents both parameters and the full return shape. The remaining gap is the absence of any routing guidance against the many sibling search/retrieval tools.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate — and it does: query is explained with concrete example phrasings ("宁德时代 业绩", "保险 增长") and top_k is given its default of 5. Only the allowed range/upper bound of top_k is left unspecified.

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 states a specific verb and resource (搜索券商研报) plus the retrieval mechanism (基于语义向量检索), and enumerates the fields returned (机构、股票、行业、评级、盈利预测). This is clearly distinct from generic knowledge search, though it never names the sibling tools (rag_search_knowledge, user_knowledge_search) it must be chosen over.

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 explicit when-to-use or when-not-to-use guidance. The description implies report search, but with siblings like rag_search_knowledge, rag_ask_investment and user_knowledge_search available, the agent gets no routing criteria for picking this tool.

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